cc1: Invalid option `-fno-strict-aliasing'

What version is your gcc?  The error could be because your gcc is too old.

Oracle.h:135: parse error before `OCIXMLType'

You could replace the -c with -E (="stop after the preprocessing stage") in that long command line, i.e.

gcc -B/usr/ccs/bin/ -E ... Oracle.c > preprocessed

and then look in preprocessed for the respective line that corresponds to Oracle.h:135 in order to figure out why the compiler thinks there's an error before OCIXMLType.  Sometimes, such errors are the result of some macro having been expanded incorrectly, or not at all.


In reply to Re: DBD::Oracle install errors by almut
in thread DBD::Oracle install errors by hbm

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.