[ISSUE] bootstrap fails for missing debuginfod

[ISSUE] bootstrap fails for missing debuginfod

[pullmoll]

[-- 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.

Re: bootstrap fails for missing debuginfod

[q66]

[-- 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

Re: bootstrap fails for missing debuginfod

[pullmoll]

[-- 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.

Re: bootstrap fails for missing debuginfod

[q66]

[-- 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

Re: bootstrap fails for missing debuginfod

[pullmoll]

[-- 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.

Re: bootstrap fails for missing debuginfod

[q66]

[-- 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

Re: bootstrap fails for missing debuginfod

[pullmoll]

[-- 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.

Re: bootstrap fails for missing debuginfod

[pullmoll]

[-- 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.

Re: bootstrap fails for missing debuginfod

[q66]

[-- 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

Re: bootstrap fails for missing debuginfod

[pullmoll]

[-- 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.

Re: bootstrap fails for missing debuginfod

[pullmoll]

[-- 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)

Re: bootstrap fails for missing debuginfod

[pullmoll]

[-- 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 &lt;gottox@voidlinux.org&gt;</string>
                <key>pkgver</key>
                <string>binutils-2.34_1</string>
                <key>run_depends</key>
                <array>
                        <string>zlib&gt;=1.2.3_1</string>
                        <string>glibc&gt;=2.29_1</string>
                        <string>libdebuginfod&gt;=0.182_1</string>
                        <string>libstdc++&gt;=4.4.0_1</string>
                        <string>libgcc&gt;=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>
```

Re: bootstrap fails for missing debuginfod

[ericonr]

[-- 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...

Re: bootstrap fails for missing debuginfod

[pullmoll]

[-- 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*

Re: bootstrap fails for missing debuginfod

[pullmoll]

[-- 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.

Re: bootstrap fails for missing debuginfod

[pullmoll]

[-- 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.

Re: bootstrap fails for missing debuginfod

[q66]

[-- 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...

Re: bootstrap fails for missing debuginfod

[pullmoll]

[-- 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.

Re: bootstrap fails for missing debuginfod

[pullmoll]

[-- 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...

Re: bootstrap fails for missing debuginfod

[pullmoll]

[-- 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)

Re: [ISSUE] [CLOSED] bootstrap fails for missing debuginfod

[q66]

[-- 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.