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

[Wichmann, Mats D]

Gordon.Schumacher at seagate.com wrote:
> "Wichmann, Mats D" <mats.d.wichmann at intel.com> wrote on 06/22/2007
> 04:28:22 PM:
> 
> # On feisty?  That's surprising... the default is 4.1.2 afaik.
> # Do you have special values for LSBCC and LSBCXX in your #
> environment? 
> 
> No, but I do remember that I had issues when I was using a 4.x
> compiler in the LSB environment.  I don't remember what anymore -
> though perhaps it was the math.h/exception issue I already found and
> fixed. 
> 
> # these are the libs you built, right? I'm still expecting those
> # got built with what at the bottom what a 4.1 compiler with the
> # stack protection code turned on; is there a chance it's picking
> # up system versions of those libraries?
> 
> No, but now that I'm rebuilding them I've discovered that indeed,
> I failed to specify CC and CXX when I ran configure.  *sigh*
> 
> The silly thing is that the way I know this is because I was no
> longer getting thirty warnings on every file about a lot of
> undefined preprocessor symbols (__ia64__, __s390x__, __powerpc__,
> etc.) 

yeah, that's irritating; I'm not sure why the script that
generates the headers generates them that way but it ought
to be an easy fix to shut it up (#if -> #if defined).