in reply to Problems installing DBD::mysql on Solaris 10

The problem seems to be indicated by the line:
gcc: language c99=none not recognized
If you look above, you see one of the options passed to gcc is:
-xc99=none
which, according to the manual I have here of gcc (3.2.3) isn't a valid option for -x. -x none is though.

I do not know where this option came from, and I neither have Solaris nor MySQL present to further investigate. You might want to edit the generated Makefile by hand, and see if the -x can be eliminated easily. If so, rip it out and run make again.

Perl --((8:>*
  • Comment on Re: Problems installing DBD::mysql on Solaris 10

Replies are listed 'Best First'.
Re^2: Problems installing DBD::mysql on Solaris 10
by graq (Curate) on Nov 02, 2005 at 16:51 UTC
    I played a little with the -x options; there are three of them and my version of gcc doesn't seem to like any of them.

    If I run

    /.cpan/build/DBD-mysql-3.0002> make gcc -c -I/opt/lib/perl5/site_perl/5.8.7/sun4-solaris/auto/DBI/ -I/usr +/local/mysql/mysql/include -mt -D_FORTEC_ -DDBD_MYSQL_INSERT_ID_IS_GO +OD -g -fno-strict-aliasing -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_ +BITS=64 -O -DVERSION=\"3.0002\" -DXS_VERSION=\"3.0002\" -fPIC "-I +/opt/lib/perl5/5.8.7/sun4-solaris/CORE" dbdimp.c cc1: error: invalid option `t' *** Error code 1 make: Fatal error: Command failed for target `dbdimp.o'
    I get this 'cc1' error.. maybe there is something dreadfully wrong with my compiler?
      Solaris, isn't? Where do you have your gcc and assorted binaries installed, and where is it in your PATH? Make sure they appear in your PATH before the Solaris binaries.
      Perl --((8:>*
        root@testboot49:/> echo $PATH /opt/bin:/opt/csw/bin:/usr/ccs/bin:/opt/sfw/bin:/usr/sbin:/usr/bin root@testboot49:/> which gcc /opt/sfw/bin/gcc root@testboot49:/> which cc no cc in /opt/bin /opt/csw/bin /usr/ccs/bin /opt/sfw/bin /usr/sbin /us +r/bin
        My big worry is the '-x' options being used. I don't understand why make (Config.pm ?) wants to use them (how it decided on those options) and it worries me that gcc doesn't like them.

        I don't really know what is going on now, and am really stuck. Is the problem with my perl installation, mysql, gcc or something else?