Re: Please test gub

[Alexander Kobel]

Hi,

strace according to Knut's instructions is attached.

On 31.01.19 12:54, Werner LEMBERG wrote:
> > > Apart from that minor buzz, `make lilypond` does a good chunk of work,
> > > but fails building tools::guile; log attached.
> >
> > I see. libtools segfauls.
>
> >     ../libtool: line 950: 23645 Segmentation fault      (core dumped)
> >     ar cru .libs/libguile.a [...]
>
> This is probably the same bug I've encountered on my openSUSE box.
> Try to remove the file (or link) `/usr/lib/bfd-plugins/LLVMgold.so'
> and replace it with the gcc variant `liblto_plugin.so'.  On my system
> I had to do
>
>    cd /usr/lib/bfd-plugins
>    ln -s /usr/lib64/gcc/x86_64-suse-linux/7/liblto_plugin.so .

Indeed, LLVMgold.so pops up in the trace.
On my system, the symlink for liblto_plugin.so already exists, so I only 
had to remove (rename wasn't enough) LLVMgold.so.

Building tools::guile succeeds after that modification; I'll test the 
further progress of `make lilypond` later.


FWIW:

# pacman -Qo /usr/lib/bfd-plugins/{LLVMgold.so,liblto_plugin.so}
/usr/lib/bfd-plugins/LLVMgold.so is owned by llvm-libs 7.0.1-2
/usr/lib/bfd-plugins/liblto_plugin.so is owned by gcc 8.2.1+20181127-1

So probably deinstalling llvm-libs (and clang, and some other packages 
that depend on it) might help... :-/

BTW, since gcc7 was mentioned couple of times in this thread:
/usr/lib/bfd-plugins/liblto_plugin.so points to 
/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/liblto_plugin.so, but I also have 
the gcc7-libs variant under 
/usr/lib/gcc/x86_64-pc-linux-gnu/7.4.1/liblto_plugin.so; but the build 
succeeded with gcc8's liblto_plugin.so, so I did not test that.


I don't quite get why (IIUC, which I might not) gub apparently builds 
gcc, but then seems to use the system-wide gcc down the road?


Cheers,
Alex

TP.21085.xz
Description: application/xz

smime.p7s
Description: S/MIME Cryptographic Signature