* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
@ 2020-04-21 22:16 ` xtraeme
2020-04-21 22:18 ` xtraeme
` (25 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: xtraeme @ 2020-04-21 22:16 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 291 bytes --]
New comment by xtraeme on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617442403
Comment:
Well, in my system this wasn't true with musl.
Anyway I don't agree in depending in texinfo for bootstrapping. Just find a way to not require it.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
2020-04-21 22:16 ` xtraeme
@ 2020-04-21 22:18 ` xtraeme
2020-04-21 22:35 ` pullmoll
` (24 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: xtraeme @ 2020-04-21 22:18 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 333 bytes --]
New comment by xtraeme on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617443025
Comment:
NOTE texinfo is optional and should not be required for "./xbps-src bootstrap".
This is why I removed it. If any of the `bootstrap` pkgs fails due to missing `texinfo` it needs to be fixed.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
2020-04-21 22:16 ` xtraeme
2020-04-21 22:18 ` xtraeme
@ 2020-04-21 22:35 ` pullmoll
2020-04-21 22:35 ` pullmoll
` (23 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: pullmoll @ 2020-04-21 22:35 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617448566
Comment:
After a bootstrap you need to rebuild bot `glibc` and `gcc` anyway, because some of the submodules are not built (e.g. `gcc-fortran`, `gcc-objc`, `gcc-go`, …). The same applies for glibc which in the bootstrapped version does not require any of `bison`, `perl`, `python3`, or `texinfo`, but only when it is built again in a chroot environment with those packages available.
Thus this PR is invalid in that it tries to remove the distinction between bootstrapped and rebuilt core packages. The bootstrap was conceived to be as minimalistic as possible. Building up an entire repository of packages requires some bootstrap packages being rebuilt in a working chroot environment.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (2 preceding siblings ...)
2020-04-21 22:35 ` pullmoll
@ 2020-04-21 22:35 ` pullmoll
2020-04-21 22:38 ` xtraeme
` (22 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: pullmoll @ 2020-04-21 22:35 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617448566
Comment:
After a bootstrap you need to rebuild both `glibc` and `gcc` anyway, because some of the submodules are not built (e.g. `gcc-fortran`, `gcc-objc`, `gcc-go`, …). The same applies for glibc which in the bootstrapped version does not require any of `bison`, `perl`, `python3`, or `texinfo`, but only when it is built again in a chroot environment with those packages available.
Thus this PR is invalid in that it tries to remove the distinction between bootstrapped and rebuilt core packages. The bootstrap was conceived to be as minimalistic as possible. Building up an entire repository of packages requires some bootstrap packages being rebuilt in a working chroot environment.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (3 preceding siblings ...)
2020-04-21 22:35 ` pullmoll
@ 2020-04-21 22:38 ` xtraeme
2020-04-21 22:49 ` fosslinux
` (21 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: xtraeme @ 2020-04-21 22:38 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 319 bytes --]
New comment by xtraeme on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617449549
Comment:
Exactly what @pullmoll said. I've built past week everything via "./xbps-src bootstrap" and I made sure texinfo wasn't required! it should not be required at all in the host.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (4 preceding siblings ...)
2020-04-21 22:38 ` xtraeme
@ 2020-04-21 22:49 ` fosslinux
2020-04-21 22:52 ` pullmoll
` (20 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: fosslinux @ 2020-04-21 22:49 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
New comment by fosslinux on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617452566
Comment:
Hm, ok. It seems I misunderstood the way the bootstrap is meant to work. I like that it should be as minimalistic as possible.
Let me just clarify; the right way forward with m4 is to remove the need for texinfo when `./xbps-src bootstrap` is run? (ie, remove the doc generation?)
What is the correct way to then make m4 use texinfo inside the chroot? Would it be the creation of a `chroot-m4` package?
@xtraeme You say bootstrap vs chroot case in your review comments - how do you distinguish between the two?
Sorry for the questions, I think I'm missing something.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (5 preceding siblings ...)
2020-04-21 22:49 ` fosslinux
@ 2020-04-21 22:52 ` pullmoll
2020-04-21 22:54 ` fosslinux
` (19 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: pullmoll @ 2020-04-21 22:52 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 445 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617453434
Comment:
> @xtraeme You say bootstrap vs chroot case in your review comments - how do you distinguish between the two?
Let me answer this: `if [ -z "$CHROOT_READY" ]; then` you are in a bootstrap.
You see this in e.g. `srcpkgs/glibc/template` where `texinfo` is a host dependency only if `$CHROOT_READY`.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (6 preceding siblings ...)
2020-04-21 22:52 ` pullmoll
@ 2020-04-21 22:54 ` fosslinux
2020-04-21 22:59 ` xtraeme
` (18 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: fosslinux @ 2020-04-21 22:54 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 416 bytes --]
New comment by fosslinux on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617454032
Comment:
Ahhhh, I see! Right, I will modify this PR to do it the proper way - remove the need for m4 to have texinfo in the bootstrap. And, for glibc to not use `/usr/share/info` during the bootstrap, but use it in the chroot (assuming that as xtrame says it is used in the chroot).
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (7 preceding siblings ...)
2020-04-21 22:54 ` fosslinux
@ 2020-04-21 22:59 ` xtraeme
2020-04-21 23:08 ` pullmoll
` (17 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: xtraeme @ 2020-04-21 22:59 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
New comment by xtraeme on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617455626
Comment:
hmm @pullmoll I think we can improve gcc:
- create a `gcc-stage0` (or whatever) for bootstrap, this should not conflict with the standard `gcc` and should only provide C/C++ support.
- make `gcc` not a bootstrap pkg anymore.
This way we shouldn't need to use `-f` while building `gcc` in the chroot.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (8 preceding siblings ...)
2020-04-21 22:59 ` xtraeme
@ 2020-04-21 23:08 ` pullmoll
2020-04-21 23:10 ` xtraeme
` (16 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: pullmoll @ 2020-04-21 23:08 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617458013
Comment:
@xtraeme LFS even has 3 builds of gcc: [pass1](http://www.linuxfromscratch.org/lfs/view/stable/chapter05/gcc-pass1.html) and [pass2](http://www.linuxfromscratch.org/lfs/view/stable/chapter05/gcc-pass2.html) in the preparation stages, then [another build](http://www.linuxfromscratch.org/lfs/view/stable/chapter06/gcc.html) in the final stage.
I have not taken a closer look as to why they do it that way, though.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (9 preceding siblings ...)
2020-04-21 23:08 ` pullmoll
@ 2020-04-21 23:10 ` xtraeme
2020-04-21 23:16 ` fosslinux
` (15 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: xtraeme @ 2020-04-21 23:10 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 368 bytes --]
New comment by xtraeme on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617458608
Comment:
@pullmoll I think we don't need this, simply setting `--enable-bootstrap` should be good enough, and I think it's enabled by default. This builds a minimal gcc and builds two more times and then compare them for a final result.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (10 preceding siblings ...)
2020-04-21 23:10 ` xtraeme
@ 2020-04-21 23:16 ` fosslinux
2020-04-21 23:17 ` pullmoll
` (14 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: fosslinux @ 2020-04-21 23:16 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 471 bytes --]
New comment by fosslinux on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617460329
Comment:
@pullmoll , the first two passes are to completely remove any references to the host system in the initial toolchain. The last build is for the final system. They do the two-pass thing in the initial toolchain as they have speical things that --enable-bootstrap can't do for them. AFAICT, all void needs is `--enable-bootstrap`.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (11 preceding siblings ...)
2020-04-21 23:16 ` fosslinux
@ 2020-04-21 23:17 ` pullmoll
2020-04-21 23:19 ` xtraeme
` (13 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: pullmoll @ 2020-04-21 23:17 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 324 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617460406
Comment:
@xtraeme that would make bootstrapping a tad easier to understand and handle for a newbie, sure. Basically you could strip all language options from the gcc template and be done, no?
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (12 preceding siblings ...)
2020-04-21 23:17 ` pullmoll
@ 2020-04-21 23:19 ` xtraeme
2020-04-21 23:21 ` xtraeme
` (12 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: xtraeme @ 2020-04-21 23:19 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 244 bytes --]
New comment by xtraeme on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617461208
Comment:
I'm not sure why they don't use `--enable-bootstrap`, maybe it's just a leftover from old gcc versions.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (13 preceding siblings ...)
2020-04-21 23:19 ` xtraeme
@ 2020-04-21 23:21 ` xtraeme
2020-04-21 23:22 ` pullmoll
` (11 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: xtraeme @ 2020-04-21 23:21 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 225 bytes --]
New comment by xtraeme on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617461604
Comment:
ah I see, it's because pass1 builds without glibc and then pass2 is built with glibc
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (14 preceding siblings ...)
2020-04-21 23:21 ` xtraeme
@ 2020-04-21 23:22 ` pullmoll
2020-04-21 23:23 ` xtraeme
` (10 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: pullmoll @ 2020-04-21 23:22 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 299 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617461865
Comment:
Yes, I just read that too. They build stage1 with newlib instead of glibc to also distangle (or dis-entangle?) any possible connection between gcc and glibc.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (15 preceding siblings ...)
2020-04-21 23:22 ` pullmoll
@ 2020-04-21 23:23 ` xtraeme
2020-04-21 23:24 ` xtraeme
` (9 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: xtraeme @ 2020-04-21 23:23 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 205 bytes --]
New comment by xtraeme on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617462189
Comment:
I haven't seen any artifacts by using our way on these years :-)
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (16 preceding siblings ...)
2020-04-21 23:23 ` xtraeme
@ 2020-04-21 23:24 ` xtraeme
2020-04-21 23:26 ` pullmoll
` (8 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: xtraeme @ 2020-04-21 23:24 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 245 bytes --]
New comment by xtraeme on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617462485
Comment:
to build a compiler you need a compiler and a C compiler needs libc headers... so why complicate things?
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (17 preceding siblings ...)
2020-04-21 23:24 ` xtraeme
@ 2020-04-21 23:26 ` pullmoll
2020-04-21 23:28 ` xtraeme
` (7 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: pullmoll @ 2020-04-21 23:26 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 367 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617463270
Comment:
LFS is very pedantic about checking their build results, which tended to be a _Good Thing™_ in the past. Also `make check` everything may look like overkill while it could save you from looking way too surprised later on :)
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (18 preceding siblings ...)
2020-04-21 23:26 ` pullmoll
@ 2020-04-21 23:28 ` xtraeme
2020-04-21 23:31 ` xtraeme
` (6 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: xtraeme @ 2020-04-21 23:28 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 360 bytes --]
New comment by xtraeme on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617463645
Comment:
The `--enable-bootstrap` GCC configure option is all what we need. GCC build system is clever enough these days to perform a reliable build that does not depend on the host system once the 3 generated compiler is built.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (19 preceding siblings ...)
2020-04-21 23:28 ` xtraeme
@ 2020-04-21 23:31 ` xtraeme
2020-04-21 23:35 ` pullmoll
` (5 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: xtraeme @ 2020-04-21 23:31 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 204 bytes --]
New comment by xtraeme on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617464546
Comment:
The issue with the `gcc-stage0` idea is that we need `gnat` :-)
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (20 preceding siblings ...)
2020-04-21 23:31 ` xtraeme
@ 2020-04-21 23:35 ` pullmoll
2020-04-21 23:36 ` pullmoll
` (4 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: pullmoll @ 2020-04-21 23:35 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617465446
Comment:
@xtraeme I think Ada can be built with `gcc` later on, using the binary from `adacore.com` for `x86_64` and making all cross compilers depend on `gcc`, not `gcc-stage0`.
Of course this does not allow for a `x86_64-musl` native build of `gcc` but requires a cross build from `x86_64` ;-P
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (21 preceding siblings ...)
2020-04-21 23:35 ` pullmoll
@ 2020-04-21 23:36 ` pullmoll
2020-04-21 23:47 ` pullmoll
` (3 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: pullmoll @ 2020-04-21 23:36 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617465446
Comment:
@xtraeme I think Ada can be built with `gcc` later on, using the binary from `adacore.com` for `x86_64` and making all cross compilers depend on `gcc`, not `gcc-stage0`.
Of course this does not allow for an (initial) `x86_64-musl` native build of `gcc` but requires a cross build from `x86_64` ;-P .. or a previously built `gcc-ada` and `libada` in the host.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (22 preceding siblings ...)
2020-04-21 23:36 ` pullmoll
@ 2020-04-21 23:47 ` pullmoll
2020-04-22 0:33 ` fosslinux
` (2 subsequent siblings)
26 siblings, 0 replies; 28+ messages in thread
From: pullmoll @ 2020-04-21 23:47 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617465446
Comment:
@xtraeme I think Ada can be built with `gcc` later on, using the binary from `adacore.com` for `x86_64` and making all cross compilers depend on `gcc`, not `gcc-stage0`.
Of course this does not allow for an (initial) `x86_64-musl` native build of `gcc` but requires a cross build from `x86_64` ;-P .. or a previously built `gcc-ada` and `libada` in the host.
Edit: I just thought about: didn't we have a way to pull in a minimal glibc for the `x86_64-musl` environment? Then perhaps the `adacore.com` binary `gnat` could also be run in `x86_64-musl` environment.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (23 preceding siblings ...)
2020-04-21 23:47 ` pullmoll
@ 2020-04-22 0:33 ` fosslinux
2020-04-22 0:36 ` pullmoll
2020-04-22 0:36 ` [PR PATCH] [Closed]: " pullmoll
26 siblings, 0 replies; 28+ messages in thread
From: fosslinux @ 2020-04-22 0:33 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 199 bytes --]
New comment by fosslinux on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617480363
Comment:
@pullmoll @xtraeme Are you good for me to close this PR?
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (24 preceding siblings ...)
2020-04-22 0:33 ` fosslinux
@ 2020-04-22 0:36 ` pullmoll
2020-04-22 0:36 ` [PR PATCH] [Closed]: " pullmoll
26 siblings, 0 replies; 28+ messages in thread
From: pullmoll @ 2020-04-22 0:36 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 218 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/21226#issuecomment-617481123
Comment:
`./xbps-src bootstrap` should succeed for glibc again, thus closing this PR.
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: [PR PATCH] [Closed]: ./xbps-src bootstrap fixes
2020-04-21 22:14 [PR PATCH] ./xbps-src bootstrap fixes fosslinux
` (25 preceding siblings ...)
2020-04-22 0:36 ` pullmoll
@ 2020-04-22 0:36 ` pullmoll
26 siblings, 0 replies; 28+ messages in thread
From: pullmoll @ 2020-04-22 0:36 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
There's a closed pull request on the void-packages repository
./xbps-src bootstrap fixes
https://github.com/void-linux/void-packages/pull/21226
Description:
I found a few missing/broken things while testing `./xbps-src bootstrap`:
1. `bootstrap` requires texinfo on the host.
2. glibc doesn't contain usr/share/info.
3. m4 was broken.
Closes #21163 . Thanks to @rovenmaccorp
^ permalink raw reply [flat|nested] 28+ messages in thread