unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Pavel Shlyak <p.shlyak@pantherx.org>, 55665@debbugs.gnu.org
Subject: bug#55665: GCC fails to cross-compile
Date: Fri, 10 Mar 2023 21:17:16 +0100	[thread overview]
Message-ID: <87edpwbbub.fsf@jpoiret.xyz> (raw)
In-Reply-To: <F2F3481B-8C63-4783-9DF3-39A42EBA6257@pantherx.org>

[-- Attachment #1: Type: text/plain, Size: 808 bytes --]

Hi Pavel,

Pavel Shlyak <p.shlyak@pantherx.org> writes:

> It seems to be still there, even after dfda2cc5f6a57a0b89b98f389a2f28bf1e94eaa4

Now that we're working on the core-updates branch, the issue is still
there.  Roughly, libgcc relies on defines that were introduced in GCC
12, so libgcc has to be compiled with GCC 12, but we have no immediate
way of doing that since we have a GCC 11 cross-compiler that built a GCC
12 host compiler which isn't usable by the builder.

It seems like the proper (but annoying) option would instead be to build
a GCC 12 cross-compiler for the builder using the builder GCC 11, then
use that to build a host GCC 12 and libgcc.  That is at odds with how
we do cross-compilation in general though :( We'll keep poking at it.

Best,
-- 
Josselin Poiret

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]

      reply	other threads:[~2023-03-10 20:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3FE14B6E-5184-4DE2-AE0B-9CF068CCB1AD@pantherx.org>
2022-05-30 10:20 ` bug#55665: GCC fails to cross-compile Pavel Shlyak
2022-08-11 18:57 ` Pavel Shlyak
2023-03-10 20:17   ` Josselin Poiret via Bug reports for GNU Guix [this message]

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=87edpwbbub.fsf@jpoiret.xyz \
    --to=bug-guix@gnu.org \
    --cc=55665@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=p.shlyak@pantherx.org \
    /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).