Re: [lfs-dev] Inaccuracy in chroot page

2020-03-14 Thread Thomas Trepl via lfs-dev
Am Samstag, den 14.03.2020, 18:11 +0100 schrieb Pierre Labastie via lfs-dev: > Le 14/03/2020 à 17:36, Bruce Dubbs via lfs-dev a écrit : > > On 3/14/20 10:55 AM, Pierre Labastie via lfs-dev wrote: > > > Le 14/03/2020 à 16:00, Bruce Dubbs via lfs-dev a écrit : > > > > On 3/14/20 3:41 AM, Pierre

Re: [lfs-dev] Inaccuracy in chroot page

2020-03-14 Thread Pierre Labastie via lfs-dev
Le 14/03/2020 à 17:36, Bruce Dubbs via lfs-dev a écrit : > On 3/14/20 10:55 AM, Pierre Labastie via lfs-dev wrote: >> Le 14/03/2020 à 16:00, Bruce Dubbs via lfs-dev a écrit : >>> On 3/14/20 3:41 AM, Pierre Labastie via lfs-dev wrote: In "6.4 Entering the Chroot Environment", we have:

Re: [lfs-dev] Inaccuracy in chroot page

2020-03-14 Thread Bruce Dubbs via lfs-dev
On 3/14/20 10:55 AM, Pierre Labastie via lfs-dev wrote: Le 14/03/2020 à 16:00, Bruce Dubbs via lfs-dev a écrit : On 3/14/20 3:41 AM, Pierre Labastie via lfs-dev wrote: In "6.4 Entering the Chroot Environment", we have:  From this point on, there is no need to use the LFS variable

Re: [lfs-dev] Inaccuracy in chroot page

2020-03-14 Thread Pierre Labastie via lfs-dev
Le 14/03/2020 à 16:00, Bruce Dubbs via lfs-dev a écrit : > On 3/14/20 3:41 AM, Pierre Labastie via lfs-dev wrote: >> In "6.4 Entering the Chroot Environment", we have: >> >>  From this point on, there is no need to use the LFS variable anymore, >> because >> all work will be restricted

Re: [lfs-dev] Inaccuracy in chroot page

2020-03-14 Thread Bruce Dubbs via lfs-dev
On 3/14/20 3:41 AM, Pierre Labastie via lfs-dev wrote: In "6.4 Entering the Chroot Environment", we have: From this point on, there is no need to use the LFS variable anymore, because all work will be restricted to the LFS file system. This is because the Bash shell is told that $LFS

Re: [lfs-dev] Ordering of Chapter 5 GGC Pass2 required external packages stanza

2020-03-14 Thread Pierre Labastie via lfs-dev
Le 14/03/2020 à 09:56, Kevin Buckley via lfs-dev a écrit : > I note, because my PkgUser Book has explicit sections for > unpacking the sources that the vanilla book doesn't, that, > in Chapter 5 GGC Pass2, the order of actions prior to the > creation of the build directory is: > > > Unpack the

Re: [lfs-dev] Ordering of Chapter 5 GGC Pass2 required external packages stanza

2020-03-14 Thread Xi Ruoyao via lfs-dev
On 2020-03-14 16:56 +0800, Kevin Buckley via lfs-dev wrote: > Indeed, is there any reason why the ordering in GCC Pass 2 > couldn't be: > > > Unpack the required external packages > Change the location of GCC's default dynamic linker > On x86_64 hosts, set the default directory name for 64-bit

[lfs-dev] Ordering of Chapter 5 GGC Pass2 required external packages stanza

2020-03-14 Thread Kevin Buckley via lfs-dev
I note, because my PkgUser Book has explicit sections for unpacking the sources that the vanilla book doesn't, that, in Chapter 5 GGC Pass2, the order of actions prior to the creation of the build directory is: Unpack the required external packages Change the location of GCC's default dynamic

Re: [lfs-dev] Building Glibc without the Info pages?

2020-03-14 Thread Kevin Buckley via lfs-dev
On Thu, 12 Mar 2020 at 16:45, Pierre Labastie via lfs-dev wrote: > > Sorry, looks like there is something "magic" in glibc source, and that it is > better to use "MAKEINFO=:". See manual/Makefile in glibc source tree: > - > ifneq ($(strip $(MAKEINFO)),:) > info: $(objpfx)libc.info > endif >

[lfs-dev] Inaccuracy in chroot page

2020-03-14 Thread Pierre Labastie via lfs-dev
In "6.4 Entering the Chroot Environment", we have: From this point on, there is no need to use the LFS variable anymore, because all work will be restricted to the LFS file system. This is because the Bash shell is told that $LFS is now the root (/) directory. But it is not true