Re: [lfs-support] LFS v. 8.3 : Compiler lacks asm-goto support.. Stop.
> Message du 16/09/18 13:49 > De : "Baho Utot" > A : lfs-support@lists.linuxfromscratch.org > Copie à : > Objet : Re: [lfs-support] LFS v. 8.3 : Compiler lacks asm-goto support.. Stop. > > On 9/16/18 6:19 AM, Terence Waterhouse wrote: > > > Message du 15/09/18 19:25 > > > De : "Ken Moffat" > > A : "Terence Waterhouse" , "LFS Support List" > > > > Copie à : > > Objet : Re: [lfs-support] LFS v. 8.3 : Compiler lacks > asm-goto > support.. Stop. > > > > On Sat, Sep 15, 2018 at 05:13:23PM +0200, > Terence Waterhouse wrote: > > > > > > > > Hello all, > > > > > > > When > running right at the start of chapter 8.3 to prepare the > kernel build, I > got the > > > > following message (with no further output) : > > > > > > > > arch/x86/Makefile:184: *** Compiler lacks asm-goto support.. Stop. > > > > > > > > As far as I can make out this is an issue with kernels before > 4.5 and > the current kernel is 4.18.5. I had no > > > > build problems with gcc-8.2.0 > and no test fails. > > > > > > > Should I continue or is this critical ? > > > > > Short answer is that you cannot continue until you are able to > > > determine what has gone wrong. At the moment you can't build a > > kernel, so > you cannot boot the new system. > > > > > > Many thanks in advance > > > > > > > > > > Of course I should have written "this is an issue with gcc > versions > before 4.5" sorry for that mistake. > > > Here is the output of gcc -v > > > > > > > gcc -v > > > Using built-in specs. > > > COLLECT_GCC=gcc > > > > > COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/8.2.0/lto-wrapper > > > > Target: x86_64-pc-linux-gnu > > > Configured with: ../configure > --prefix=/usr > --enable-languages=c,c++ --disable-multilib > --disable-bootstrap > --disable-libmpx --with-system-zlib > > > Thread model: > posix > > > gcc version 8.2.0 (GCC) > > > > I've not heard of anybody hitting > this problem with recent gcc. > > Google found the patch where this was > proposed, the initial comment > > is: > > > > | Now that we have objtool to > validate the correctness of asm-goto > > | constructs we can start using it > to guarantee the absence of dynamic > > | branches (and thus speculation). > > > > > So the problem appears to be in objtool. We added elfutils to LFS > > > in 8.2 to support objtool, maybe something went wrong in your > > install of > that (libelf). > > > > The test in the kernel tree is at scripts/gcc-goto.sh, > but I don't > > know how to run that successfully from outside the kernel > build (in > > particular, it needs to be persuaded to run objtool, and > altered to > > not discard the output). > > > > You are using the orc > unwinder ? > > > > All I can suggest is that you run ldd on the compiled > objtool in the > > kernel tree (tools/objtool/objtool) to see if that reports > an error > > (it should report it is linked to libelf.so.1 as libz, libc, the > > > vdso and the loader. > > > > Unfortunately, the kernel build system has > changed this year, and > > things which used to reliably trigger the expected > error messages > > (in my experiences, trying to change the kernel config and > rebuild > > the existing tree as a user after building as root, and at first > boot > > a typo in the bootargs root=/dev/sda76, caused failures but with > > > very odd error messages. > > > > ĸen > > -- > > Tout est bien, tout va bien, > tout va pour le mieux qu'il soit possible > > -- Candide, de Voltaire > > > (Everything is for the best, in the best of all possible worlds) > > > > > Hello all and of course, Ken, > > I tried your suggestions and couldn't get > much (any) feedback. There > are only source files in the tools/objtool > directory > so ldd couldn't be much help. > > I couldn't get gcc-goto.sh to > run either. however, you mentioned > libelf so I tried recompiling the > package and it reports that > the c compiler is not working. The relevant > output from config.log is > as follow : > > > > > configure:3371: checking for gcc > configure:3387: found /usr/bin/gcc > > configure:3398: result: gcc > configure:3627: check
Re: [lfs-support] LFS v. 8.3 : Compiler lacks asm-goto support.. Stop.
> Message du 15/09/18 19:25 > De : "Ken Moffat" > A : "Terence Waterhouse" , "LFS Support List" > Copie à : > Objet : Re: [lfs-support] LFS v. 8.3 : Compiler lacks asm-goto support.. Stop. > > On Sat, Sep 15, 2018 at 05:13:23PM +0200, Terence Waterhouse wrote: > > > > > > Hello all, > > > > > When running right at the start of chapter 8.3 to prepare the kernel > > > build, I got the > > > following message (with no further output) : > > > > > arch/x86/Makefile:184: *** Compiler lacks asm-goto support.. Stop. > > > > > As far as I can make out this is an issue with kernels before 4.5 and the > > > current kernel is 4.18.5. I had no > > > build problems with gcc-8.2.0 and no test fails. > > > > > Should I continue or is this critical ? > > Short answer is that you cannot continue until you are able to > determine what has gone wrong. At the moment you can't build a > kernel, so you cannot boot the new system. > > > > Many thanks in advance > > > > > > Of course I should have written "this is an issue with gcc versions before > > 4.5" sorry for that mistake. > > Here is the output of gcc -v > > > > gcc -v > > Using built-in specs. > > COLLECT_GCC=gcc > > COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/8.2.0/lto-wrapper > > Target: x86_64-pc-linux-gnu > > Configured with: ../configure --prefix=/usr --enable-languages=c,c++ > > --disable-multilib --disable-bootstrap --disable-libmpx --with-system-zlib > > Thread model: posix > > gcc version 8.2.0 (GCC) > > I've not heard of anybody hitting this problem with recent gcc. > Google found the patch where this was proposed, the initial comment > is: > > | Now that we have objtool to validate the correctness of asm-goto > | constructs we can start using it to guarantee the absence of dynamic > | branches (and thus speculation). > > So the problem appears to be in objtool. We added elfutils to LFS > in 8.2 to support objtool, maybe something went wrong in your > install of that (libelf). > > The test in the kernel tree is at scripts/gcc-goto.sh, but I don't > know how to run that successfully from outside the kernel build (in > particular, it needs to be persuaded to run objtool, and altered to > not discard the output). > > You are using the orc unwinder ? > > All I can suggest is that you run ldd on the compiled objtool in the > kernel tree (tools/objtool/objtool) to see if that reports an error > (it should report it is linked to libelf.so.1 as libz, libc, the > vdso and the loader. > > Unfortunately, the kernel build system has changed this year, and > things which used to reliably trigger the expected error messages > (in my experiences, trying to change the kernel config and rebuild > the existing tree as a user after building as root, and at first boot > a typo in the bootargs root=/dev/sda76, caused failures but with > very odd error messages. > > ĸen > -- > Tout est bien, tout va bien, tout va pour le mieux qu'il soit possible > -- Candide, de Voltaire > (Everything is for the best, in the best of all possible worlds) > Hello all and of course, Ken, I tried your suggestions and couldn't get much (any) feedback. There are only source files in the tools/objtool directory so ldd couldn't be much help. I couldn't get gcc-goto.sh to run either. however, you mentioned libelf so I tried recompiling the package and it reports that the c compiler is not working. The relevant output from config.log is as follow : configure:3371: checking for gcc configure:3387: found /usr/bin/gcc configure:3398: result: gcc configure:3627: checking for C compiler version configure:3636: gcc --version >&5 gcc (GCC) 8.2.0 Copyright (C) 2018 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:3647: $? = 0 configure:3636: gcc -v >&5 Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/8.2.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../configure --prefix=/usr --enable-languages=c,c++ --disable-multilib --disable-bootstrap --disable-libmpx --with-system-zlib Thread model: posix gcc version 8.2.0 (GCC) configure:3647: $? = 0 configure:3636: gcc -V >&5 gcc: error: unrecognized command line option '-V' gcc: fatal error: no input files compilation terminated. configure:3647: $? = 1 configure:3636: gcc -qversion >&5 gcc: error: unrecognized command line option '-qversion'; did you mean '--version'? gcc: fatal
Re: [lfs-support] LFS v. 8.3 : Compiler lacks asm-goto support.. Stop.
> Message du 15/09/18 19:25 > De : "Ken Moffat" > A : "Terence Waterhouse" , "LFS Support List" > Copie à : > Objet : Re: [lfs-support] LFS v. 8.3 : Compiler lacks asm-goto support.. Stop. > > On Sat, Sep 15, 2018 at 05:13:23PM +0200, Terence Waterhouse wrote: > > > > > > Hello all, > > > > > When running right at the start of chapter 8.3 to prepare the kernel > > > build, I got the > > > following message (with no further output) : > > > > > arch/x86/Makefile:184: *** Compiler lacks asm-goto support.. Stop. > > > > > As far as I can make out this is an issue with kernels before 4.5 and the > > > current kernel is 4.18.5. I had no > > > build problems with gcc-8.2.0 and no test fails. > > > > > Should I continue or is this critical ? > > Short answer is that you cannot continue until you are able to > determine what has gone wrong. At the moment you can't build a > kernel, so you cannot boot the new system. > > > > Many thanks in advance > > > > > > Of course I should have written "this is an issue with gcc versions before > > 4.5" sorry for that mistake. > > Here is the output of gcc -v > > > > gcc -v > > Using built-in specs. > > COLLECT_GCC=gcc > > COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/8.2.0/lto-wrapper > > Target: x86_64-pc-linux-gnu > > Configured with: ../configure --prefix=/usr --enable-languages=c,c++ > > --disable-multilib --disable-bootstrap --disable-libmpx --with-system-zlib > > Thread model: posix > > gcc version 8.2.0 (GCC) > > I've not heard of anybody hitting this problem with recent gcc. > Google found the patch where this was proposed, the initial comment > is: > > | Now that we have objtool to validate the correctness of asm-goto > | constructs we can start using it to guarantee the absence of dynamic > | branches (and thus speculation). > > So the problem appears to be in objtool. We added elfutils to LFS > in 8.2 to support objtool, maybe something went wrong in your > install of that (libelf). > > The test in the kernel tree is at scripts/gcc-goto.sh, but I don't > know how to run that successfully from outside the kernel build (in > particular, it needs to be persuaded to run objtool, and altered to > not discard the output). > > You are using the orc unwinder ? > > All I can suggest is that you run ldd on the compiled objtool in the > kernel tree (tools/objtool/objtool) to see if that reports an error > (it should report it is linked to libelf.so.1 as libz, libc, the > vdso and the loader. > > Unfortunately, the kernel build system has changed this year, and > things which used to reliably trigger the expected error messages > (in my experiences, trying to change the kernel config and rebuild > the existing tree as a user after building as root, and at first boot > a typo in the bootargs root=/dev/sda76, caused failures but with > very odd error messages. > > ĸen > -- > Tout est bien, tout va bien, tout va pour le mieux qu'il soit possible > -- Candide, de Voltaire > (Everything is for the best, in the best of all possible worlds) > Many thanks for the reply Ken. I found the patch on google you speak of, but I'm afraid I'm out of my depth here. I'll look into your post in detail and see where I can go. I'll just say that since I began 8.3 All went smoothly and all test suites succeeded I had no fails whatsoever so I don't have much idea as to where to start searching. I had only one path problem probably caused by an omission on my part. (See the post: chapter 6.55 v.8.3 fatal error while building e2fsprogs in the support-list ) which Pierre Labastié fixed for me so perhaps I'll start there. Many thanks for your reply Best regards Terence -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
Re: [lfs-support] LFS v. 8.3 : Compiler lacks asm-goto support.. Stop.
> Message du 15/09/18 16:51 > De : "Terence Waterhouse" > A : "lfs-support" > Copie à : > Objet : [lfs-support] LFS v. 8.3 : Compiler lacks asm-goto support.. Stop. > > > Hello all, > When running right at the start of chapter 8.3 to prepare the kernel build, I > got the > following message (with no further output) : > arch/x86/Makefile:184: *** Compiler lacks asm-goto support.. Stop. > As far as I can make out this is an issue with kernels before 4.5 and the > current kernel is 4.18.5. I had no > build problems with gcc-8.2.0 and no test fails. > Should I continue or is this critical ? > Many thanks in advance > Terence. -- >http://lists.linuxfromscratch.org/listinfo/lfs-support >FAQ: http://www.linuxfromscratch.org/blfs/faq.html >Unsubscribe: See the above information page >Do not top post on this list. >A: Because it messes up the order in which people normally read text. >Q: Why is top-posting such a bad thing? >A: Top-posting. >Q: What is the most annoying thing in e-mail? >http://en.wikipedia.org/wiki/Posting_style Of course I should have written "this is an issue with gcc versions before 4.5" sorry for that mistake. Here is the output of gcc -v gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/8.2.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../configure --prefix=/usr --enable-languages=c,c++ --disable-multilib --disable-bootstrap --disable-libmpx --with-system-zlib Thread model: posix gcc version 8.2.0 (GCC) -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
[lfs-support] LFS v. 8.3 : Compiler lacks asm-goto support.. Stop.
Hello all, When running right at the start of chapter 8.3 to prepare the kernel build, I got the following message (with no further output) : arch/x86/Makefile:184: *** Compiler lacks asm-goto support.. Stop. As far as I can make out this is an issue with kernels before 4.5 and the current kernel is 4.18.5. I had no build problems with gcc-8.2.0 and no test fails. Should I continue or is this critical ? Many thanks in advance Terence. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
Re: [lfs-support] chapter 6.55 v.8.3 fatal error while building e2fsprogs
> Message du 13/09/18 19:17
> De : "Terence Waterhouse"
> A : "LFS Support List"
> Copie à :
> Objet : Re: [lfs-support] chapter 6.55 v.8.3 fatal error while building
> e2fsprogs
>
> Bonsoir Pierre ! I just got back from shopping to find your mail. It was
> exactly that. A masterly reply! I did as you said and the build went like a
> dream. No tests failed, so I'm back in business. I must say that I thought
> (and hoped !) it may be something on those lines but I would never have found
> it, I fear, without help. Nonetheless, I marked that long list of commands as
> needing care, especially when tired. . . and thought that I had done them
> correctly, but I really must have skipped the last ln commands, there is no
> other answer. Many thanks for your time, Bonsoir et mille mercis Terence
> > Message du 13/09/18 16:05 > De : "Pierre Labastie" > A :
> lfs-support@lists.linuxfromscratch.org > Copie à : > Objet : Re:
> [lfs-support] chapter 6.55 v.8.3 fatal error while building e2fsprogs > > On
> 9/13/18 3:37 PM, Terence Waterhouse wrote: > Hello everyone, > > This is my
> second attempt to build LFS and everything went more than smoothly. All the
> builds and test suites gave all the desired results. > > Now while building
> e2fsprogs in section 6.55 I get a fatal error. Here's the relevant code : > >
> /// > ... > making all in lib/support > make[2]: Entering
> directory '/sources/e2fsprogs-1.44.3/build/lib/support' > SUBST
> ../../lib/dirpaths.h > CC ../../../lib/support/cstring.c > CC
> ../../../lib/support/mkquota.c > CC ../../../lib/support/plausible.c >
> ../../../lib/support/plausible.c:38:10: fatal error: blkid/blkid.h: No such
> file or directory > #include "blkid/blkid.h" > ^~~ >
> compilation terminated. > make[2]: *** [Makefile:386: plausible.o] Error 1 >
> make[2]: Leaving directory '/sources/e2fsprogs-1.44.3/build/lib/support' >
> make[1]: *** [Makefile:419: all-libs-recursive] Error 1 > make[1]: Leaving
> directory '/sources/e2fsprogs-1.44.3/build' > make: *** [Makefile:341: all]
> Error 2 Looks like something in 6.6 - Creating Essential files and Symlinks
> has been overlooked. Check that all the commands~: ln -svf
> /tools/include/blkid /usr/include ln -svf /tools/include/libmount
> /usr/include ln -svf /tools/include/uuid /usr/include install -vdm755
> /usr/lib/pkgconfig for pc in blkid mount uuid do sed 's@tools@usr@g'
> /tools/lib/pkgconfig/${pc}.pc \ > /usr/lib/pkgconfig/${pc}.pc done --
> have been executed correctly. I think blkid, uuid, etc are not used before
> e2fsprogs, so that's why there was no failure before. I'd say also that you
> do not need to start again chapter 6. Just run those commands now, specially
> the "ln -sfv" ones, and try again to build e2fsprogs (don't forget to remove
> the whole build tree and to untar again e2fsprogs). Regards Pierre --
> http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ:
> http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above
> information page Do not top post on this list. A: Because it messes up the
> order in which people normally read text. Q: Why is top-posting such a bad
> thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
> http://en.wikipedia.org/wiki/Posting_style --
> http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ:
> http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above
> information page Do not top post on this list. A: Because it messes up the
> order in which people normally read text. Q: Why is top-posting such a bad
> thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
> http://en.wikipedia.org/wiki/Posting_style
Sorry for the top posting in the last mail, I shall end up getting the hang of
it.--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
Re: [lfs-support] chapter 6.55 v.8.3 fatal error while building e2fsprogs
Bonsoir Pierre !
I just got back from shopping to find your mail. It was exactly that. A
masterly reply! I did as you said and the build went like a dream. No tests
failed, so I'm back in business.
I must say that I thought (and hoped !) it may be something on those lines but
I would never have found it, I fear, without help. Nonetheless, I marked that
long list of commands as needing care, especially when tired. . . and thought
that I had done them correctly, but I really must have skipped the last ln
commands, there is no other answer.
Many thanks for your time,
Bonsoir et mille mercis
Terence
> Message du 13/09/18 16:05
> De : "Pierre Labastie"
> A : lfs-support@lists.linuxfromscratch.org
> Copie à :
> Objet : Re: [lfs-support] chapter 6.55 v.8.3 fatal error while building
> e2fsprogs
>
> On 9/13/18 3:37 PM, Terence Waterhouse wrote: > Hello everyone, > > This is
> my second attempt to build LFS and everything went more than smoothly. All
> the builds and test suites gave all the desired results. > > Now while
> building e2fsprogs in section 6.55 I get a fatal error. Here's the relevant
> code : > > /// > ... > making all in lib/support > make[2]:
> Entering directory '/sources/e2fsprogs-1.44.3/build/lib/support' > SUBST
> ../../lib/dirpaths.h > CC ../../../lib/support/cstring.c > CC
> ../../../lib/support/mkquota.c > CC ../../../lib/support/plausible.c >
> ../../../lib/support/plausible.c:38:10: fatal error: blkid/blkid.h: No such
> file or directory > #include "blkid/blkid.h" > ^~~ >
> compilation terminated. > make[2]: *** [Makefile:386: plausible.o] Error 1 >
> make[2]: Leaving directory '/sources/e2fsprogs-1.44.3/build/lib/support' >
> make[1]: *** [Makefile:419: all-libs-recursive] Error 1 > make[1]: Leaving
> directory '/sources/e2fsprogs-1.44.3/build' > make: *** [Makefile:341: all]
> Error 2 Looks like something in 6.6 - Creating Essential files and Symlinks
> has been overlooked. Check that all the commands~: ln -svf
> /tools/include/blkid /usr/include ln -svf /tools/include/libmount
> /usr/include ln -svf /tools/include/uuid /usr/include install -vdm755
> /usr/lib/pkgconfig for pc in blkid mount uuid do sed 's@tools@usr@g'
> /tools/lib/pkgconfig/${pc}.pc \ > /usr/lib/pkgconfig/${pc}.pc done --
> have been executed correctly. I think blkid, uuid, etc are not used before
> e2fsprogs, so that's why there was no failure before. I'd say also that you
> do not need to start again chapter 6. Just run those commands now, specially
> the "ln -sfv" ones, and try again to build e2fsprogs (don't forget to remove
> the whole build tree and to untar again e2fsprogs). Regards Pierre --
> http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ:
> http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above
> information page Do not top post on this list. A: Because it messes up the
> order in which people normally read text. Q: Why is top-posting such a bad
> thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
> http://en.wikipedia.org/wiki/Posting_style
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
Re: [lfs-support] Info on package bzip2-1.0.6 in LFS 8.2
> Message du 06/09/18 18:30 > De : "Thomas Trepl" > A : "LFS Support List" > Copie à : > Objet : Re: [lfs-support] Info on package bzip2-1.0.6 in LFS 8.2 > > Am Donnerstag, den 06.09.2018, 18:03 +0200 schrieb Terence Waterhouse: > > > > > > Message du 06/09/18 18:00 > > > De : "Michael Shell" > > > A : lfs-support@lists.linuxfromscratch.org > > > Copie à : > > > Objet : > > > Re: [lfs-support] Info on package bzip2-1.0.6 in LFS 8.2 > > > > > > On > > > Thu, 6 Sep 2018 16:11:22 +0200 (CEST) Terence Waterhouse > > wrote: > > > > https://lwn.net/Articles/762264/ From > > that article, someone setup a > > > bzip2 gitlab page: > > ... > > > Interesting and important information > > > Michael. Thank you. Perhaps > > the gzip option might seem more reliable? > > > But I am not qualified to > > answer that. > Hi guys, first, please have > > > a look to the mail format you use. It's quite hard to read. Simply text > > > format would be appropriate, no html required. Regarding bzip2: We as LFS > > > cannot "switch back" to gzip as many packages are provided bz2 > > > compressed. Because of that, we need the bzip2 package in the book. > > > Otherwise we would not be able to uncompress .bz2 files which might cause > > > trouble, even more when coming to BLFS. The disapperance of bzip2.org > > > happened timely just between 8.2 and 8.3. In 8.2 we have the old link > > > (previously working well) and in the 8.3, we allready use another > > > location (LFSs own server). So, if you nowadays use 8.2 (which is > > > perfectly ok), you fill stumble over that issue that bzip2.org > > > disappeared. We will not change 8.2 or earlier versions of the book as it > > > is something like "modifying the past". -- Thomas -- > > > http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: > > > http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above > > > information page Do not top post on this list. A: Because it messes up > > > the order in which people normally read text. Q: Why is top-posting such > > > a bad thing? A: Top-posting. Q: What is the most annoying thing in > > > e-mail? http://en.wikipedia.org/wiki/Posting_style Thanks Thomas, as I found a copy and am now into chapter 6 I will try to get to the end of this build using LFS 8.2. However, for future builds I will of course move on. . . For Hazel I confirm that the link provided by Bruce works with no problem for me. Thanks also to Bruce for the pertinent reminders of the caveats regarding repositories in chapter 3. Had I looked back I would probably have saved everyone some time ! Perhaps this thread is solved now and can be closed ? Many thanks to all for the prompt replies Terence -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
Re: [lfs-support] Info on package bzip2-1.0.6 in LFS 8.2
> Message du 06/09/18 17:37 > De : "Douglas R. Reno" > A : "LFS Support List" > Copie à : > Objet : Re: [lfs-support] Info on package bzip2-1.0.6 in LFS 8.2 > > > > On Thu, Sep 6, 2018 at 10:30 AM Hazel Russman wrote: > On Thu, 6 Sep 2018 16:11:22 +0200 (CEST) > Terence Waterhouse wrote: > > > Dear sir, > > > > > > > > Although I have been using exclusively Linux for many many years it is only > > a few days ago I decided to buils my own system using LFS v.8.2. I am not > > quite certain which list this post should actually be on, but I subscribed > > to this list because I shall probably need it later... I do not generally > > post unnecessary questions, and indeed, I don't post questions at all. So > > here goes : > > > > > > > > Building LFS 8.2 went smoothly until section 5.18 bzip2-1.0.6. When I tried > > to untar the package I got the following output: > > > > > > > > tar: This does not look like a tar archive gzip: > > > > stdin: not in gzip format > > > > tar: Child returned status 1 > > > > tar: Error is not recoverable: exiting now > > > > > > > > In fact it is apparently a html file according to 'file' output with a > > tar.gz extension. I first downloaded the original packages with the > > wget-list file, then, meeting this problem, ran wget with the specific file > > name. No succes. I tried the site http//:www.bzip.org and could find no > > trace of the sources. A visit to the site will tell you why. > > > > > > > > I tried all the usual tricks to unpack it with absolutely no succes. To cut > > things short I spent 2 days searching the web to no avail then sent off a > > desperate search for "what happened to bzip2?" This search produced the > > following link : > > > > > > > > https://lwn.net/Articles/762264/ > > > > > > > > I also found on this page the following link to the source files of bzip2 > > and it is the only link I have been able to find: > > > > > > > > https://web.archive.org/web/2014073512/http://www.bzip.org/1.0.6/bzip2-1.0.6.tar.gz > > > > > > > > Download > > > > replace the package obtained from wget-list > > > > untar > > > > and carry on as usual. > > > > > > > > I might attract your attention to the fact that the post at lwn.net is > > dated August 9th 2018 and so is recent. > > > > > > > > As LFS uses bzip2 extensively it seemed to me that this information might > > be of some use. I can only hope that the newly downloaded version works. . > > . > > > > > > > > Many many thanks for the great work, I will let you know if I run into any > > difficulties with the package. > > > > I leave it to your judgement as to how to address this potentially > > important issue. > > > > > > > > Yours sincerely > > > > > > > > Terence Waterhouse > > > I just checked. It's not on Anduin. There's a link but it leads nowhere. > That's strange because I had no problem finding it in 8.3-rc2. > > -- > Hazel Russman > > > Guys/Gals, > Check out this link - http://ftp.gnome.org/pub/gnome/teams/releng/tarballs-needing-help/bzip2/bzip2-1.0.6.tar.gz > GNOME has it as well :-) -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style Thank you Douglas ! I will keep this safely bookmarked ! Terence -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
Re: [lfs-support] Info on package bzip2-1.0.6 in LFS 8.2
> Message du 06/09/18 17:30 > De : "Hazel Russman" > A : lfs-support@lists.linuxfromscratch.org > Copie à : > Objet : Re: [lfs-support] Info on package bzip2-1.0.6 in LFS 8.2 > > On Thu, 6 Sep 2018 16:11:22 +0200 (CEST) Terence Waterhouse wrote: > Dear > sir, > > > > Although I have been using exclusively Linux for many many > years it is only a few days ago I decided to buils my own system using LFS > v.8.2. I am not quite certain which list this post should actually be on, but > I subscribed to this list because I shall probably need it later... I do not > generally post unnecessary questions, and indeed, I don't post questions at > all. So here goes : > > > > Building LFS 8.2 went smoothly until section > 5.18 bzip2-1.0.6. When I tried to untar the package I got the following > output: > > > > tar: This does not look like a tar archive gzip: > > stdin: > not in gzip format > > tar: Child returned status 1 > > tar: Error is not > recoverable: exiting now > > > > In fact it is apparently a html file > according to 'file' output with a tar.gz extension. I first downloaded the > original packages with the wget-list file, then, meeting this problem, ran > wget with the specific file name. No succes. I tried the site > http//:www.bzip.org and could find no trace of the sources. A visit to the > site will tell you why. > > > > I tried all the usual tricks to unpack it > with absolutely no succes. To cut things short I spent 2 days searching the > web to no avail then sent off a desperate search for "what happened to > bzip2?" This search produced the following link : > > > > > https://lwn.net/Articles/762264/ > > > > I also found on this page the > following link to the source files of bzip2 and it is the only link I have > been able to find: > > > > > https://web.archive.org/web/2014073512/http://www.bzip.org/1.0.6/bzip2-1.0.6.tar.gz > > > > > Download > > replace the package obtained from wget-list > > untar > > > and carry on as usual. > > > > I might attract your attention to the > fact that the post at lwn.net is dated August 9th 2018 and so is recent. > > > > > As LFS uses bzip2 extensively it seemed to me that this information > might be of some use. I can only hope that the newly downloaded version > works. . . > > > > Many many thanks for the great work, I will let you know > if I run into any difficulties with the package. > > I leave it to your > judgement as to how to address this potentially important issue. > > > > > Yours sincerely > > > > Terence Waterhouse > I just checked. It's not on > Anduin. There's a link but it leads nowhere. That's strange because I had no > problem finding it in 8.3-rc2. -- Hazel Russman -- > http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: > http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above > information page Do not top post on this list. A: Because it messes up the > order in which people normally read text. Q: Why is top-posting such a bad > thing? A: Top-posting. Q: What is the most annoying thing in e-mail? > http://en.wikipedia.org/wiki/Posting_style No, as I said the only version I could find was at web.archive.org. When I started 8.3 was not available, so the issue has perhaps already been addressed? I shall continue with 8.2, as my present build is for educational purposes above all. Sorry for the top posting in the first post, and for the "sir"... regards Terence Waterhouse-- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
[lfs-support] Info on package bzip2-1.0.6 in LFS 8.2
Dear sir, Although I have been using exclusively Linux for many many years it is only a few days ago I decided to buils my own system using LFS v.8.2. I am not quite certain which list this post should actually be on, but I subscribed to this list because I shall probably need it later... I do not generally post unnecessary questions, and indeed, I don't post questions at all. So here goes : Building LFS 8.2 went smoothly until section 5.18 bzip2-1.0.6. When I tried to untar the package I got the following output: tar: This does not look like a tar archive gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error is not recoverable: exiting now In fact it is apparently a html file according to 'file' output with a tar.gz extension. I first downloaded the original packages with the wget-list file, then, meeting this problem, ran wget with the specific file name. No succes. I tried the site http//:www.bzip.org and could find no trace of the sources. A visit to the site will tell you why. I tried all the usual tricks to unpack it with absolutely no succes. To cut things short I spent 2 days searching the web to no avail then sent off a desperate search for "what happened to bzip2?" This search produced the following link : https://lwn.net/Articles/762264/ I also found on this page the following link to the source files of bzip2 and it is the only link I have been able to find: https://web.archive.org/web/2014073512/http://www.bzip.org/1.0.6/bzip2-1.0.6.tar.gz Download replace the package obtained from wget-list untar and carry on as usual. I might attract your attention to the fact that the post at lwn.net is dated August 9th 2018 and so is recent. As LFS uses bzip2 extensively it seemed to me that this information might be of some use. I can only hope that the newly downloaded version works. . . Many many thanks for the great work, I will let you know if I run into any difficulties with the package. I leave it to your judgement as to how to address this potentially important issue. Yours sincerely Terence Waterhouse -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
