* [ISSUE] bootstrap fails for missing debuginfod
@ 2020-12-15 23:54 pullmoll
2020-12-16 0:05 ` q66
` (19 more replies)
0 siblings, 20 replies; 21+ messages in thread
From: pullmoll @ 2020-12-15 23:54 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 520 bytes --]
New 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`, yet `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.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
@ 2020-12-16 0:05 ` q66
2020-12-16 0:10 ` pullmoll
` (18 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: q66 @ 2020-12-16 0:05 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 173 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745648250
Comment:
but gdb is not a bootstrap package
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
2020-12-16 0:05 ` q66
@ 2020-12-16 0:10 ` pullmoll
2020-12-16 0:12 ` q66
` (17 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: pullmoll @ 2020-12-16 0:10 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 233 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745655091
Comment:
Hmm, true. I wonder why trying to `./xbps-src -N binary-bootstrap x86_64` failed, though.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod 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
` (16 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: q66 @ 2020-12-16 0:12 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 213 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745657443
Comment:
if something is pulling in gdb by accident, it needs to be found and fixed
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
` (2 preceding siblings ...)
2020-12-16 0:12 ` q66
@ 2020-12-16 0:13 ` pullmoll
2020-12-16 0:14 ` q66
` (15 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: pullmoll @ 2020-12-16 0:13 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 217 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745659473
Comment:
Currently redoing the stage0 and will then try to identify the candidate.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
` (3 preceding siblings ...)
2020-12-16 0:13 ` pullmoll
@ 2020-12-16 0:14 ` q66
2020-12-16 0:17 ` pullmoll
` (14 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: q66 @ 2020-12-16 0:14 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 232 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745661716
Comment:
okay, remember that gdb must not even be built, so if it's being built, that is already wrong
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
` (4 preceding siblings ...)
2020-12-16 0:14 ` q66
@ 2020-12-16 0:17 ` pullmoll
2020-12-16 0:20 ` pullmoll
` (13 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: pullmoll @ 2020-12-16 0:17 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 442 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745665578
Comment:
Yeah, I thought it was part of the bootstrap and did the `$CHROOT_READY` shielding for `debuginfod`, but this should then not change a thing.
Also the `bootstrap` itself actually installed the packages, but I then did `./xbps-src zap` and tried the `./xbps-src -N binary-boostrap` as I always did.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
` (5 preceding siblings ...)
2020-12-16 0:17 ` pullmoll
@ 2020-12-16 0:20 ` pullmoll
2020-12-16 0:21 ` q66
` (12 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: pullmoll @ 2020-12-16 0:20 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 453 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745665578
Comment:
Yeah, I thought it was part of the bootstrap and did the `$CHROOT_READY` shielding for `debuginfod`, but this should then not change a thing.
Also the `./xbps-src bootstrap` itself actually installed the packages, but I then did `./xbps-src zap` and tried the `./xbps-src -N binary-boostrap` as I always did.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
` (6 preceding siblings ...)
2020-12-16 0:20 ` pullmoll
@ 2020-12-16 0:21 ` q66
2020-12-16 0:22 ` pullmoll
` (11 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: q66 @ 2020-12-16 0:21 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 373 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745670397
Comment:
you don't need to binary-bootstrap after bootstrap, what you need to do is remove the binary packages and then build `base-chroot` using the masterdir, *then* zap and binary-bootstrap to proceed to stage 1, and erase the binpkgs again
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
` (7 preceding siblings ...)
2020-12-16 0:21 ` q66
@ 2020-12-16 0:22 ` pullmoll
2020-12-16 0:26 ` pullmoll
` (10 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: pullmoll @ 2020-12-16 0:22 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 334 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745672577
Comment:
Sure, this would have been the next step anyway. I've done it many times. So the difference is I cannot use a set of stage0 packages to do a `binary-bootstrap`. That used to work previously.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
` (8 preceding siblings ...)
2020-12-16 0:22 ` pullmoll
@ 2020-12-16 0:26 ` pullmoll
2020-12-16 0:53 ` pullmoll
` (9 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: pullmoll @ 2020-12-16 0:26 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 270 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745678650
Comment:
So I'll try the stage1 next.
[stage0-files.txt](https://github.com/void-linux/void-packages/files/5699479/stage0-files.txt)
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
` (9 preceding siblings ...)
2020-12-16 0:26 ` pullmoll
@ 2020-12-16 0:53 ` pullmoll
2020-12-16 0:56 ` ericonr
` (8 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: pullmoll @ 2020-12-16 0:53 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 2084 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745692444
Comment:
Peeking at the stage0 `x86_64-repodata` I see it is the `binutils` referring to `debuginfod`:
```xml
<key>binutils</key>
<dict>
<key>architecture</key>
<string>x86_64</string>
<key>filename-sha256</key>
<string>3618d892f6c72dbfd156649d2777f617e727bd7bd3ca6a89e65c889bd01483d1</string>
<key>filename-size</key>
<integer>5650737</integer>
<key>homepage</key>
<string>http://www.gnu.org/software/binutils/</string>
<key>installed_size</key>
<integer>27194915</integer>
<key>license</key>
<string>GPL-3.0-or-later</string>
<key>maintainer</key>
<string>Enno Boland <gottox@voidlinux.org></string>
<key>pkgver</key>
<string>binutils-2.34_1</string>
<key>run_depends</key>
<array>
<string>zlib>=1.2.3_1</string>
<string>glibc>=2.29_1</string>
<string>libdebuginfod>=0.182_1</string>
<string>libstdc++>=4.4.0_1</string>
<string>libgcc>=4.4.0_1</string>
</array>
<key>shlib-requires</key>
<array>
<string>libz.so.1</string>
<string>libdl.so.2</string>
<string>libc.so.6</string>
<string>libdebuginfod.so.1</string>
<string>libstdc++.so.6</string>
<string>libgcc_s.so.1</string>
<string>libpthread.so.0</string>
</array>
<key>short_desc</key>
<string>GNU binary utilities</string>
</dict>
```
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
` (10 preceding siblings ...)
2020-12-16 0:53 ` pullmoll
@ 2020-12-16 0:56 ` ericonr
2020-12-16 0:58 ` pullmoll
` (7 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: ericonr @ 2020-12-16 0:56 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 256 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745693295
Comment:
I have a PR to add that (https://github.com/void-linux/void-packages/pull/26502) but it hasn't been merged yet...
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
` (11 preceding siblings ...)
2020-12-16 0:56 ` ericonr
@ 2020-12-16 0:58 ` pullmoll
2020-12-16 1:00 ` pullmoll
` (6 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: pullmoll @ 2020-12-16 0:58 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 214 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745693978
Comment:
Um, let me check what I took from your `musl-1.2.0` branch.. *blushes*
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
` (12 preceding siblings ...)
2020-12-16 0:58 ` pullmoll
@ 2020-12-16 1:00 ` pullmoll
2020-12-16 1:03 ` pullmoll
` (5 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: pullmoll @ 2020-12-16 1:00 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 273 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745693978
Comment:
Um, let me check what I took from your `musl-1.2.0` branch.. *blushes*
Edit: no, that PR isn't merged in my `musl-1.2.1` branch.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
` (13 preceding siblings ...)
2020-12-16 1:00 ` pullmoll
@ 2020-12-16 1:03 ` pullmoll
2020-12-16 1:05 ` q66
` (4 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: pullmoll @ 2020-12-16 1:03 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 441 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745693978
Comment:
Um, let me check what I took from your `musl-1.2.0` branch.. *blushes*
Edit: no, that PR isn't merged in my `musl-1.2.1` branch.
Edit2: Still it seems this has crept in from my system into the `binutils` build this or that way. Some configure script looking for host installed libraries I think.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
` (14 preceding siblings ...)
2020-12-16 1:03 ` pullmoll
@ 2020-12-16 1:05 ` q66
2020-12-16 1:08 ` pullmoll
` (3 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: q66 @ 2020-12-16 1:05 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 267 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745696218
Comment:
looks like we need to explicitly *disable* `debuginfod` when not `CHROOT_READY` to prevent host system from affecting it then...
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
` (15 preceding siblings ...)
2020-12-16 1:05 ` q66
@ 2020-12-16 1:08 ` pullmoll
2020-12-16 1:10 ` pullmoll
` (2 subsequent siblings)
19 siblings, 0 replies; 21+ messages in thread
From: pullmoll @ 2020-12-16 1:08 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 179 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745697019
Comment:
Yes, that should solve the problem.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
` (16 preceding siblings ...)
2020-12-16 1:08 ` pullmoll
@ 2020-12-16 1:10 ` pullmoll
2020-12-16 1:49 ` pullmoll
2020-12-26 2:44 ` [ISSUE] [CLOSED] " q66
19 siblings, 0 replies; 21+ messages in thread
From: pullmoll @ 2020-12-16 1:10 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 304 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745697019
Comment:
Yes, that should solve the problem.
Being able to binary-bootstrap stage0 can be helpful in case you need to redo a stage1 because of bugs in your templates...
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
` (17 preceding siblings ...)
2020-12-16 1:10 ` pullmoll
@ 2020-12-16 1:49 ` pullmoll
2020-12-26 2:44 ` [ISSUE] [CLOSED] " q66
19 siblings, 0 replies; 21+ messages in thread
From: pullmoll @ 2020-12-16 1:49 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 264 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/27190#issuecomment-745710456
Comment:
For completeness sake
[stage1-files.txt](https://github.com/void-linux/void-packages/files/5699787/stage1-files.txt)
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [ISSUE] [CLOSED] bootstrap fails for missing debuginfod
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod pullmoll
` (18 preceding siblings ...)
2020-12-16 1:49 ` pullmoll
@ 2020-12-26 2:44 ` q66
19 siblings, 0 replies; 21+ messages in thread
From: q66 @ 2020-12-26 2:44 UTC (permalink / raw)
To: ml
[-- 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.
^ permalink raw reply [flat|nested] 21+ messages in thread
end of thread, other threads:[~2020-12-26 2:44 UTC | newest]
Thread overview: 21+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-15 23:54 [ISSUE] bootstrap fails for missing debuginfod 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 ` [ISSUE] [CLOSED] " q66
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).