This is the mail archive of the mailing list for the binutils project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Question about ld tests requiring plugins support

On Tue, Aug 26, 2014 at 5:32 PM, Nicholas Clifton <> wrote:
> Hi Bin,
>> I ran into ld/lto testing failures of my arm/aarch64 toolchain.  The
>> BFD: tmpdir/lto-12c.o: plugin needed to handle lto object
> Try recreating your toolchain.  This time add "--enable-plugins" to the
> configure command line.

Hi Nick, thanks for helping.  I tried with that both for gcc and
binutils, but no luck.

After looking into lto.exp, I found below code snippet.

set plugin_names {
set plug_opt ""
foreach plug $plugin_names {
    set plug_so [run_host_cmd $CC "--print-file-name $plug"]
    if { $plug_so ne $plug } then {
    set plug_opt "--plugin $plug_so"

For my toolchain, the check always output the file name, rather than
the full path of the plugins.

Even file "" does exist in the installation place:

That's why "--plugin ...." is set to empty string.

Interesting thing is gcc manually says that:

-print-file-name=libraryPrint the full absolute name of the library
file library that would be used when linking--and don't do anything
else. With this option, GCC does not compile or link anything; it just
prints the file name.

> Cheers
>   Nick

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]