[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#48913: i686-linux-gnu cross-compiler cannot find libgcc_s [core-upda
From: |
Maxime Devos |
Subject: |
bug#48913: i686-linux-gnu cross-compiler cannot find libgcc_s [core-updates] |
Date: |
Sat, 19 Jun 2021 09:37:27 +0200 |
User-agent: |
Evolution 3.34.2 |
Ludovic Courtès schreef op vr 18-06-2021 om 11:33 [+0200]:
> Maxime Devos <maximedevos@telenet.be> skribis:
>
> > I have found a solution: passing --with-slibdir to GCC's configure
> > script. Not sure if that's the proper solution though. GNU Hello
> > now builds succesfully! I'll test with a few more packages later
> > and then ‘formally’ submit the patch (after writing a commit message).
>
> Could you check whether aarch64-linux-gnu or armhf-linux-gnueabihf (say)
> have the problem, and whether this patch addresses it?
This patch (passing --with-slibdir) doesn't actualy fully work
(when cross-compiling to i686-linux-gnu from a x86_64-linux),
as libstdc++ is not installed in the right place
(and other stuff like libusan, but those are less critical IMHO).
I sent a more complete (and hackier) patch as part of the
patch series for implementing cross-compilation in Meson
(not really the right place, I know, but it's hard to test
cross-compilation when the cross-compiler is broken),
see [PATCH v3 core-updates 36/37: Fix cross-compiler for i686-linux-gnu]
(https://issues.guix.gnu.org/49025>.
I'll send a mail to bug#49025 asking people to respond about
that patch at bug#48913, to keep things separate.
I'll test whether aarch64-linux-gnu and armhf-linux-gnueabihf
have the same problem and whether the patch (from bug#48913)
addresses it.
Greetings,
Maxime.
signature.asc
Description: This is a digitally signed message part