From: Marius Bakke <mbakke@fastmail.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Brett Gilio <brettg@gnu.org>, 38803@debbugs.gnu.org
Subject: [bug#38803] [PATCH] gnu: elfutils: Update to 0.178
Date: Thu, 06 Feb 2020 15:31:29 +0100 [thread overview]
Message-ID: <87d0ar4wji.fsf@devup.no> (raw)
In-Reply-To: <2b6c210935f4f6833cbd944dd27e31a64645b5dd.camel@klomp.org>
[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]
Mark Wielaard <mark@klomp.org> writes:
> On Thu, 2020-02-06 at 12:04 +0100, Mark Wielaard wrote:
>> BTW. Upstream is now debating some of the dependencies for other
>> distros that have bootstrapping requirements too:
>> https://sourceware.org/bugzilla/show_bug.cgi?id=25509
>
> It would be nice if someone could comment on that bug who better
> understands the bootstrap requirements for the guix toolchain. Note
> that this is relevant to other packages too because we are very eager
> to improve the debugability of the whole toolchain and so have
> submitted patches to various core packages to support debuginfod-client
> like binutils, gdb, annocheck, etc. Which means they all eventually
> depend on everything libcurl depends on:
> https://sourceware.org/elfutils/Debuginfod.html
I think that the Guix toolchain (the one used in package builds) should
stay the same (no debuginfod support), and that we should add
debuginfod-enabled variants that gets included when users install
'binutils' or 'gcc-toolchain' manually. How does that sound?
So our only concern will be how to use Elfutils' libelf.so for GCC,
which should be straightforward with an "elfutils-minimal" variant that
does not pull in the debuginfo dependencies.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-02-06 14:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 1:41 [bug#38803] [PATCH] gnu: elfutils: Update to 0.178 Mark Wielaard
2019-12-30 1:44 ` Brett Gilio
2019-12-30 2:04 ` Mark Wielaard
2020-01-12 20:39 ` Mark Wielaard
2020-01-12 20:54 ` Marius Bakke
2020-01-13 0:03 ` Mark Wielaard
2020-01-13 22:26 ` Marius Bakke
2020-01-31 12:43 ` Mark Wielaard
2020-01-31 15:49 ` Marius Bakke
2020-01-31 16:55 ` Mark Wielaard
2020-02-05 20:41 ` Marius Bakke
2020-02-06 11:04 ` Mark Wielaard
2020-02-06 11:36 ` Marius Bakke
2020-02-06 13:23 ` Mark Wielaard
2020-02-06 14:31 ` Marius Bakke [this message]
2023-09-02 18:39 ` Vagrant Cascadian
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=87d0ar4wji.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=38803@debbugs.gnu.org \
--cc=brettg@gnu.org \
--cc=mark@klomp.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 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.