[lsb-discuss] Link errors using LSB 3.0, help!

Gordon.Schumacher at seagate.com Gordon.Schumacher at seagate.com
Fri Jun 22 15:18:22 PDT 2007

"Wichmann, Mats D" <mats.d.wichmann at intel.com> wrote on 06/22/2007 03:47:54

# Gordon.Schumacher at seagate.com wrote:
# > But it looked like -fno-stack-protector isn't implemented until
# > GCC 4.x?  So how does one accomplish that?
# You can pass this option yourself.  Inside lsbcc we do actually
# figure out the compiler in use, and if gcc, the version, for
# other reasons already, so we can make adding the flag version specific.

What I mean is, lsbcc is invoking GCC 3.4.6 - so I get:

root at devel:~# lsbcc -fstack-protector foo.c
cc1: error: unrecognized command line option "-fstack-protector"
root at devel:~# lsbcc -v
Reading specs from /usr/lib/gcc/i486-linux-gnu/3.4.6/specs
Configured with: ../src/configure -v --enable-languages=c,c++,f77,pascal
--prefix=/usr --libexecdir=/usr/lib
--with-gxx-include-dir=/usr/include/c++/3.4 --enable-shared
--with-system-zlib --enable-nls --without-included-gettext
--program-suffix=-3.4 --enable-__cxa_atexit --enable-clocale=gnu
--enable-libstdcxx-debug --with-tune=pentium4 i486-linux-gnu
Thread model: posix
gcc version 3.4.6 (Ubuntu 3.4.6-5ubuntu1)

So I *can't* pass this flag... I built wxWidgets using lsbcc as well.

It seems odd to me that there are only five missing references to
__stack_chk_fail, three in libwx_x11univ_html-2.8.a (htmllib_htmlfilt.o)
and two in libwx_x11univ_core-2.8.a (corelib_utilsx11.o).  Does that
make any sense?

More information about the lsb-discuss mailing list