From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] bootstrap fails for missing debuginfod
Date: Sat, 26 Dec 2020 03:44:46 +0100 [thread overview]
Message-ID: <20201226024446.jwY5smfmHscA5_7mu6KtPtN7K61VlmTtKfo_YkbsXLM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27190@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
Closed issue by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/27190
Description:
A stage0 bootstrap for `x86_64` with `kernel-libc-headers-5.10` finishes w/o errors. ~~Yet you cannot use it for a binary-bootstrap because `gdb` depends on `debuginfod`, a subpkgf of `elfutils`, but `elfutils` is not `bootstrap=yes` and so `debuginfod` is not there.
I think to solve this the `gdb` template should add `debuginfod` to the `build_options_default` iff `$CHROOT_READY` is non zero.~~
It is not `gdb` but `binutils` which need to explicitly disable debuginfod by `--without-debuginfod` in case `$CHROOT_READY` is zero.
prev parent reply other threads:[~2020-12-26 2:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 23:54 [ISSUE] " pullmoll
2020-12-16 0:05 ` q66
2020-12-16 0:10 ` pullmoll
2020-12-16 0:12 ` q66
2020-12-16 0:13 ` pullmoll
2020-12-16 0:14 ` q66
2020-12-16 0:17 ` pullmoll
2020-12-16 0:20 ` pullmoll
2020-12-16 0:21 ` q66
2020-12-16 0:22 ` pullmoll
2020-12-16 0:26 ` pullmoll
2020-12-16 0:53 ` pullmoll
2020-12-16 0:56 ` ericonr
2020-12-16 0:58 ` pullmoll
2020-12-16 1:00 ` pullmoll
2020-12-16 1:03 ` pullmoll
2020-12-16 1:05 ` q66
2020-12-16 1:08 ` pullmoll
2020-12-16 1:10 ` pullmoll
2020-12-16 1:49 ` pullmoll
2020-12-26 2:44 ` q66 [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=20201226024446.jwY5smfmHscA5_7mu6KtPtN7K61VlmTtKfo_YkbsXLM@z \
--to=q66@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).