On Mon, Sep 21, 2020 at 1:33 PM Martin Liška <mli...@suse.cz> wrote: > > On 9/10/20 1:57 PM, JonY via Gcc-patches wrote: > > On 9/10/20 9:44 AM, Richard Biener wrote: > >>> > >>> I can confirm liblto is still loaded correctly from the logs, likewise > >>> renaming it away will cause an error. > >>> > >>> Seems to be fine on Linux. > >> > >> OK then. > >> > >> Thanks, > >> Richard. > >> > > > > Thanks for reviewing, pushed to master branch > > ae6cf62861b5e9acb518b016ddbe7f783206f65f. > > > > Hello. > > I see the patch broke auto-loading support in bintuils which > automatically try to load plugins in bfd-plugins folder: > > One example: > [ 108s] ar cr libbuiltins.a builtins.o alias.o bind.o break.o builtin.o > caller.o cd.o colon.o command.o common.o declare.o echo.o enable.o eval.o > evalfile.o evalstring.o exec.o exit.o fc.o fg_bg.o hash.o help.o history.o > jobs.o kill.o let.o mapfile.o pushd.o read.o return.o set.o setattr.o shift.o > source.o suspend.o test.o times.o trap.o type.o ulimit.o umask.o wait.o > getopts.o shopt.o printf.o getopt.o bashgetopt.o complete.o > [ 108s] ar: builtins.o: plugin needed to handle lto object
Isn't that eventually just because the 'gcc' package looks for liblto_plugin.so.0.0.0 instead of liblto_plugin.so? Richard. > Thanks, > Martin
