all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 63329@debbugs.gnu.org
Subject: [bug#63329] [PATCH] gnu: Use gexps for gcc-boot0 and related packages.
Date: Sun, 07 May 2023 23:27:33 +0200	[thread overview]
Message-ID: <87y1lzg7cq.fsf_-_@gnu.org> (raw)
In-Reply-To: <7c5922aed25834bcc4cfd248a5107960f3700ae2.1683408750.git.mail@cbaines.net> (Christopher Baines's message of "Sat, 6 May 2023 22:32:30 +0100")

Hi,

Christopher Baines <mail@cbaines.net> skribis:

> There are currently problems with native or cross building for i586-gnu, and
> one factor mixed up with this is that some of the gcc packages use sexp's for
> the phases, and thus introducing gexp's has caused problems.
>
> As part of the going in circles with this, this commit switches gcc-boot0 to
> use gexp's in it's arguments, and then also modifies libstdc++-boot0,
> libstdc++-boot0-gcc7, cross-gcc-wrapper, gcc-final and make-libstdc++ to
> handle this change.
>
> If done correctly, this change shouldn't affect any derivations.
>
> * gnu/packages/commencement.scm (libstdc++-boot0, libstdc++-boot0-gcc7,
> gcc-boot0, gcc-final)[arguments]: Use gexps.
> (cross-gcc-wrapper): Use gexps in the generated package.
> * gnu/packages/gcc.scm (make-libstdc++): Use gexps in the generated package.

I’m late to the party, but I think it goes in the right direction.
Thank you!

Ludo’.




      parent reply	other threads:[~2023-05-07 21:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06 13:22 [bug#63329] [PATCH] gnu: Use gexps for gcc-boot0 and related packages Christopher Baines
2023-05-06 21:32 ` [bug#63329] [PATCH v2] " Christopher Baines
2023-05-07  8:39   ` bug#63329: " Christopher Baines
2023-05-07 21:27   ` Ludovic Courtès [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

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

  git send-email \
    --in-reply-to=87y1lzg7cq.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=63329@debbugs.gnu.org \
    --cc=mail@cbaines.net \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.