binutils version

robert baker robertmbaker at
Fri May 14 20:23:13 PDT 2010

I went ahead and did some checking on the compiler warnings that
binutils produces. There are 27 warnings that come from
binutils-2.19.51 (we already use --disable-werror in the book). There
are 30 warnings that come from binutils-2.20.

The three additional warnings that are produced are as follows:
syslex.c:1271: warning: 'yyunput' defined but not used
arlex.c:1396: warning: 'yyunput' defined but not used
ldlex.c:3362: warning: 'yyunput' defined but not used

yyunput is not defined by any code added by the pax patch. In fact
none of the warnings in either build are a result of the pax patch.
When compiling without the patch the warnings are exactly the same. As
such I don't see much reason for holding back on binutils-2.20.


On Fri, May 14, 2010 at 6:16 PM, Robert Connolly
<robert at> wrote:
> Hi.
> The PaX team doesn't have a patch for binutils-2.20, only for 2.19. The 2.19
> patch has several compiler warnings when applied to binutils-2.20. PLD and
> Gentoo use --disable-werror when building Binutils, use the old patch with
> binutils-2.20, and ignore the compiler warnings.
> The only feature in 2.20 that caught my attention was the Gold linker. Gold
> was developed to perform better than the old BFD linker. The programs that
> Gold links will perform the same. In gcc-4.5 there are link time
> optimizations (-flto) with Gold linker plugin support (-fuse-linker-plugin).
> The -fuse-linker-plugin option is used to extract objects files from static
> libraries, instead of doing this by hand, for better optimization
> from -flto. -flto alone doesn't optimize very well, and should be used
> with -fwhole-program. Not many packages support building with these options,
> so they will be rarely used for the moment.
> So, for me personally, there isn't a great deal of reason to upgrade to
> binutils-2.20, at least until PaX releases a new Binutils patch.
> Something you might want to discuss or think about.
> robert
> --
> FAQ:
> Unsubscribe: See the above information page

More information about the hlfs-dev mailing list