unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 48913@debbugs.gnu.org
Subject: bug#48913: i686-linux-gnu cross-compiler cannot find libgcc_s [core-updates]
Date: Fri, 18 Jun 2021 11:33:23 +0200	[thread overview]
Message-ID: <875yybikkc.fsf@gnu.org> (raw)
In-Reply-To: <7bf9667b405c900fb484521964c10d0a718fab04.camel@telenet.be> (Maxime Devos's message of "Tue, 08 Jun 2021 17:25:26 +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?

Thanks,
Ludo’.




  reply	other threads:[~2021-06-18  9:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08  8:41 bug#48913: i686-linux-gnu cross-compiler cannot find libgcc_s [core-updates] Maxime Devos
2021-06-08 14:23 ` Maxime Devos
2021-06-08 15:25 ` Maxime Devos
2021-06-18  9:33   ` Ludovic Courtès [this message]
2021-06-19  7:37     ` Maxime Devos
2021-06-19 10:05     ` bug#49113: aarch64-linux-gnu cross-compiler fails to build [core-updates] Maxime Devos
2021-06-20 12:17       ` Maxime Devos
2021-07-03 16:12       ` Ludovic Courtès
2021-07-04 20:33         ` Ludovic Courtès
2021-06-19 11:05     ` bug#48913: i686-linux-gnu cross-compiler cannot find libgcc_s [core-updates] Maxime Devos
2021-06-19 11:59     ` Maxime Devos
2021-06-18  9:32 ` Ludovic Courtès
2021-07-03 13:40   ` Maxime Devos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875yybikkc.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=48913@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).