[Bug other/56249] New: gcc-nm doesn't work if gcc configured with --disable-lto

[Bug other/56249] New: gcc-nm doesn't work if gcc configured with --disable-lto

[benno at benno dot id.au]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56249

             Bug #: 56249
           Summary: gcc-nm doesn't work if gcc configured with
                    --disable-lto
    Classification: Unclassified
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: other
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: benno@benno.id.au


Created attachment 29393
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29393
Only install LTO related binaries if LTO is enabled.

If you try to run gcc-nm without LTO enabled it provides an error: 

Cannot find plugin <..>/liblto_plugin.so

Now, it is reasonable to say "if you didn't configure LTO then why are you
using gcc-nm". My counter would be that I don't think it is necessary for GCC
to build gcc-nm (et. al.) unless LTO is enabled since the binaries can't
possibly work correctly.

I'd propose that these binaries are not built and installed unless LTO is
enabled. The attached patch does this.

Cheers,

Benno

[Bug other/56249] gcc-nm doesn't work if gcc configured with --disable-lto

[rguenth at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56249

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
            Version|unknown                     |4.8.0
           Keywords|                            |build, lto
   Last reconfirmed|                            |2013-02-08
                 CC|                            |rguenth at gcc dot gnu.org
     Ever Confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> 2013-02-08 08:36:17 UTC ---
As we have

ACX_ELF_TARGET_IFELSE([# ELF platforms build the lto-plugin always.
  build_lto_plugin=yes
],[if test x"$default_enable_lto" = x"yes" ; then

and thus sometimes build the plugin even with --disable-lto the build
and install should be conditionalized on whether we build/install the
plugin instead.

Btw, please post patches to gcc-patches@gcc.gnu.org