[Xorp-hackers] Compile problems for Xorp on Fedora 11.

[Bruce Simpson]

Ben Greear wrote:
>>
>> The #ident pragma is useful as it's a compiler mandated way of embedding
>> object IDs in which can then be retrieved using the 'ident' command from
>> binutils (or compatible toolchains). It even works with MinGW in 
>> Windows.
>
> What would you use this for?

Traceability -- knowing exactly which compiled objects went into a 
binary from a build.

Typically more useful in production builds, not as useful for debug 
builds, where this information is redundantly coded anyway.

>
>> Whilst #ident is not part of the current ISO C++ standard, it has been
>> generally supported by most UNIX C++ compilers for years. So this
>> strikes me more as a regression on Fedora's part.
>>
>> Can we be sure that this isn't due to a change in Fedora's shipped gcc
>> spec file?
>
> [greearb at ben-dt2 git]$ gcc --version
> gcc (GCC) 4.4.0 20090506 (Red Hat 4.4.0-4)
> Copyright (C) 2009 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There 
> is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
> PURPOSE.

What about -dumpspec ?

>
> I've no particular idea why it complains.  It seems to be only a 
> warning, but
> I think xorp is using -Werr or something like that.  Seemed easier to 
> comment
> out all the idents instead of digging further as I wasn't aware of any 
> useful
> features derived from #ident.

Which warning(s) are specifically triggered?


thans,
BMS