[Bug binutils/18482] New: inconsistent bfd-plugins directory for cross-compiler tools

[ossman at cendio dot se]

https://sourceware.org/bugzilla/show_bug.cgi?id=18482

            Bug ID: 18482
           Summary: inconsistent bfd-plugins directory for cross-compiler
                    tools
           Product: binutils
           Version: 2.25
            Status: NEW
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: ossman at cendio dot se
  Target Milestone: ---

The path to the bfd-plugins directory is computed a bit wonky when you're
building binutils for cross-compilation, resulting in it looking in two
different locations depending on how you call it.

Basically it always looks for it as <progdir>/../lib/bfd-plugins. The problem
is that <progdir> will be <bindir> if you call <target>-nm, but <tooldir>/bin
if you call nm (in the tooldir directory). IOW, e.g. an ARM cross compiler will
look in these two places:

    /usr/bin/../bin/../lib/bfd-plugins
    /usr/arm-none-linux-gnueabi/bin/../bin/../lib/bfd-plugins

Besides the fact that I now have to dump plugins in two places, I'm also
concerned that all my different binutils share /usr/lib/bfd-plugins. Does gcc's
LTO plugin handle every possible target? Or will I have to put every gcc's
plugin in there under different names? And will binutils pick the right one?

I'd suggest to use the tooldir directory for cross-compilers in order to avoid
confusion.

-- 
You are receiving this mail because:
You are on the CC list for the bug.