GNOME Bugzilla – Bug 616001
vte 0.24.0 fails to build with the Sun Studio compiler
Last modified: 2012-04-12 23:05:10 UTC
The addition of the "-fno-common" argument to the MAYBE_WARN variable in vte's configure.in file is causing VTE to fail to configure when building with the Sun Studio compiler. This is because the Sun Studio cc generates this warning, but a zero return code when building with this argument: cc: Warning: Option -fno-common passed to ld, if ld is invoked, ignored otherwise usage: cc [ options] files. Use 'cc -flags' for details So the configure fails when checking for termcap with this error (from config.log): configure:25857: checking for tgetent in -ltermcap configure:25892: /usr/bin/cc -o conftest -I/usr/include/ncurses -i -xO4 -xspace -xstrconst -xpentium -mr -xregs=no%frameptr -I/usr/include/ncurses -fno-common -Wl,-zignore -Wl,-zcombreloc -Wl,-Bdirect -L/usr/gnu/lib -R/usr/gnu/lib conftest.c -ltermcap >&5 cc: Warning: Option -fno-common passed to ld, if ld is invoked, ignored otherwise "conftest.c", line 54: warning: statement not reached ld: fatal: auxiliary filter option (-f, --auxiliary) is only available when building a shared object ld: fatal: flags processing errors Could this option be removed from the MAYBE_WARN list, or only added if GCC is being used?
Got a patch? :)
On our build system we patch the configure.in script to remove the "-fno-common" reference from the configure.in script. There are a lot of examples of how to more properly add compiler specific arguments in a configure script.
I think this is fixed on vte-0-32, please check.