unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 39941@debbugs.gnu.org
Subject: bug#39941: Disk-image size increase on core-updates.
Date: Sun, 15 Mar 2020 18:13:52 +0100	[thread overview]
Message-ID: <87tv2pilrj.fsf@gnu.org> (raw)
In-Reply-To: <875zf5lv79.fsf@gmail.com> (Mathieu Othacehe's message of "Sun, 15 Mar 2020 12:21:46 +0100")

Hi!

Congrats on this, Mathieu!

Mathieu Othacehe <m.othacehe@gmail.com> skribis:

> You'll find a trimmed patch attached. I found the GCC patch upstream
> (pushed in January), after finding the option in the online manual.

[...]

> From d8c45710847b504912670ebccf319354746f06f9 Mon Sep 17 00:00:00 2001
> From: Mathieu Othacehe <m.othacehe@gmail.com>
> Date: Sat, 14 Mar 2020 11:39:52 +0100
> Subject: [PATCH] gnu: cross-gcc: Add a "lib" output.
>
> Add a "lib" output to cross-gcc. This requires an upstream GCC patch adding
> support for --with-toolexeclibdir configure option. This option allows to
> install cross-built GCC libraries in a specific location.
>
> This also fixes the computation of TOOLDIR_BASE_PREFIX, that fails when
> /gnu/store/... directories are involved.

Perhaps add “Fixes <https://bugs.gnu.org/39941>.”


[...]

> +     ;; TOOLDIR_BASE_PREFIX is erroneous when using a separate "lib"
> +     ;; output. Specify it correctly, otherwise GCC won't find its shared
> +     ;; libraries installed in the "lib" output.

How erroneous is it?  Is there a bug report we could link to?

> +++ b/gnu/packages/patches/gcc-7-cross-toolexeclibdir.patch
> @@ -0,0 +1,2654 @@
> +This patch taken from GCC upstream adds support for overriding cross-compiled
> +shared libraries installation path.  This is needed to have a separate "lib"
> +output containing those shared libraries.

Could you add a link to the web view of the commit, if possible?

From this patch, I think we should keep only the generated bit
(‘configure’ and ‘Makefile.in’ files) and discard everything else.  We
can probably also discard changes in bundled libraries (zlib, libgc,
etc.).

The comment should mention that we’ve stripped things compared to the
upstream commit.

Apologies for suggesting some more tedious work, but I think it’ll be
helpful!  :-)

Thank you!

Ludo’.

  reply	other threads:[~2020-03-15 17:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-06  7:37 bug#39941: Disk-image size increase on core-updates Mathieu Othacehe
2020-03-10  9:22 ` Mathieu Othacehe
2020-03-11 14:25   ` Ludovic Courtès
2020-03-11 14:45     ` Mathieu Othacehe
2020-03-11 20:33       ` Ludovic Courtès
2020-03-12  8:06         ` Mathieu Othacehe
2020-03-14 10:54         ` Mathieu Othacehe
2020-03-14 12:30           ` Marius Bakke
2020-03-15 11:21             ` Mathieu Othacehe
2020-03-15 17:13               ` Ludovic Courtès [this message]
2020-03-17 11:28                 ` Mathieu Othacehe
2020-03-24 10:54                   ` Ludovic Courtès
2020-03-24 17:01                     ` Mathieu Othacehe
2020-03-25 21:34                       ` Ludovic Courtès

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=87tv2pilrj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=39941@debbugs.gnu.org \
    --cc=m.othacehe@gmail.com \
    /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).