Re: [lfs-support] LFS-9.0 5.24. Gettext-0.20.1 build error
On 1/5/20 12:10 PM, Bruce Dubbs wrote: On 1/5/20 8:01 AM, Scott Andrews wrote: This is what I used in the build: ./configure --disable-shared make -j1 The result: [snip] make[2]: Entering directory '/mnt/lfs/source/gettext-0.20.1/gettext-tools/src' here=`pwd`; \ cd ../../libtextstyle/lib && \ make install-nobase_includeHEADERS install-nobase_nodist_includeHEADERS includedir="$here" make[3]: Entering directory '/mnt/lfs/usr/src/LFS-RPi/BUILD/gettext-0.20.1/libtextstyle/lib' make[3]: *** No rule to make target 'install-nobase_includeHEADERS'. Stop. I'm not sure what is happening here. This is what I have in the same area: cd ../../libtextstyle/lib && \ make install-nobase_includeHEADERS install-nobase_nodist_includeHEADERS includedir="$here" make[6]: Entering directory '/mnt/lfs/sources/gettext-0.20.1/libtextstyle/lib' /tools/bin/mkdir -p '/mnt/lfs/sources/gettext-0.20.1/gettext-tools/src' /tools/bin/install -c -m 644 textstyle.h '/mnt/lfs/sources/gettext-0.20.1/gettext-tools/src/.' /tools/bin/mkdir -p '/mnt/lfs/sources/gettext-0.20.1/gettext-tools/src' /tools/bin/mkdir -p '/mnt/lfs/sources/gettext-0.20.1/gettext-tools/src/textstyle' ... What I do see in your log is Entering directory '/mnt/lfs/usr/src/LFS-RPi/BUILD... So the system is a Raspberry Pi? Yes it is a Raspberry pi 2, LFS-8.4 builds and works well on it as it has been my IMAP/emails server sine version 8.4 came out. I am trying to update the build to version 9.0 then make a desktop. I'm wondering why you have: Entering /mnt/lfs/source/gettext-0.20.1/gettext-tools/src followed by Entering /mnt/lfs/usr/src/LFS-RPi/BUILD/... I'll have to check that, I am currently rebuilding gettext on the pi2, I may os had an issue with the build scripts and the working directories. -- Bruce -- 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-9.0 5.24. Gettext-0.20.1 build error
On 1/5/20 12:25 PM, Flareon Zulu wrote: On January 5, 2020, at 09:51, Scott Andrews wrote: > >On 1/5/20 3:35 AM, Pierre Labastie wrote: >> Le 05/01/2020 à 05:37, Bruce Dubbs a écrit : >>> On 1/4/20 7:45 PM, Ken Moffat wrote: On Sat, Jan 04, 2020 at 05:11:18PM -0500, Scott Andrews wrote: > On 1/4/20 1:45 PM, Flareon Zulu wrote: >> On January 4, 2020, at 09:47, Scott Andrews >> wrote: >> >>> Anyone have this error? >>> ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o >>> m-regex.o mbrlen.o regex.o >>> ranlib libgrep.a >>> make[3]: Leaving directory >>> '/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep' >>> Making all in src >>> here=`pwd`; \ >>> cd ../../libtextstyle/lib && \ >>> /usr/bin/make install-nobase_includeHEADERS >>> install-nobase_nodist_includeHEADERS includedir="$here" >>> make[3]: *** No rule to make target 'install-nobase_includeHEADERS'. >> Stop. >>> make[2]: *** [Makefile:3955: textstyle.h] Error 2 >>> make[1]: *** [Makefile:2173: all-recursive] Error 1 >>> make: *** [Makefile:2041: all] Error 2 >>> Didn't see anything on the list about this >>> Gettext-0.19.8.1 is ok >>> -- >> Especially in light of this: https://savannah.gnu.org/bugs/?56333 >> >> It seems there could be an issue with build order, essentially. I didn't >> have an issue, but some people online have had this happen, they're just >> not on this list. >> >> Flareon Zulu >> > Could very well be, I will follow up on the link you posted and see if I > caqn make sense in it. > > The usual workaround for what that sounds like is "make -j1". Apologies if you are already doing that. My most recent example of that was in bison on a Skylake (an i3 so I'd been running make -j4 : perhaps -j3 or -j2 might have sufficed). On other machines (haswell i7, ryzen 3400G) make -j8 was fine. Modern CPUs can be a pain. And that is another thing to learn from LFS - ISTR that dropping back to -j1 in case of problems is mentioned in the FAQ. >>> In section 4.5. About SBUs, the last sentence in the note: >>> >>> "If you run into a problem with a build step, revert back to a single >>> processor build to properly analyze the error messages." >>> >>> This may be the cause of the error, but I think it is unlikely. The last >>> release of gettext was in May and we certainly would have run into the problem >>> before this if it has a race condition. >>> >> Hmmm, in our automated build (jhalfs), gettext used to be blacklisted for >> optimizations (means it was compiled with make -j1), until December 21st, when >> I've removed blacklist in jhalfs. I've built several times since then at -j8 >> on a Haswell, so gettext can be compilled at -j8 on that CPU, but maybe, as >> Ken mentioned, modern CPU's could do something different... If there is more >> evidence that there is a race condition in gettext, I'll blacklist it again. >> >> Pierre >This is what I used in the build: >./configure --disable-shared >make -j1 >The result: >rm -f libgrep.a >ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o >m-regex.o mbrlen.o regex.o >ranlib libgrep.a >make[3]: Leaving directory >'/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep' >make[2]: Leaving directory >'/mnt/lfs/source/BUILD/gettext-0.20.1/gettext-tools/libgrep' >Making all in src >make[2]: Entering directory >'/mnt/lfs/source/gettext-0.20.1/gettext-tools/src' >here=`pwd`; \ >cd ../../libtextstyle/lib && \ > make install-nobase_includeHEADERS >install-nobase_nodist_includeHEADERS includedir="$here" >make[3]: Entering directory >'/mnt/lfs/usr/src/LFS-RPi/BUILD/gettext-0.20.1/libtextstyle/lib' >make[3]: *** No rule to make target 'install-nobase_includeHEADERS'. Stop. >make[3]: Leaving directory >'/mnt/lfs/usr/src/LFS-RPi/BUILD/gettext-0.20.1/libtextstyle/lib' >make[2]: *** [Makefile:3955: textstyle.h] Error 2 >make[2]: Leaving directory >'/mnt/lfs/usr/src/LFS-RPi/BUILD/gettext-0.20.1/gettext-tools/src' >make[1]: *** [Makefile:2173: all-recursive] Error 1 >make[1]: Leaving directory >'/mnt/lfs/usr/src/LFS-RPi/BUILD/gettext-0.20.1/gettext-tools' >make: *** [Makefile:2041: all] Error 2 >-- >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 My next suggestion in this saga is to try plain "make" if you didn't already. Otherwise, I'm stumped. Could we bug upstream about this? I am looking at the build for Fedora 31 rpm spec file they have a patch in the source rpm and some other stuff. I am looking at
Re: [lfs-support] LFS-9.0 5.24. Gettext-0.20.1 build error
On January 5, 2020, at 09:51, Scott Andrews wrote: > >On 1/5/20 3:35 AM, Pierre Labastie wrote: >> Le 05/01/2020 à 05:37, Bruce Dubbs a écrit : >>> On 1/4/20 7:45 PM, Ken Moffat wrote: On Sat, Jan 04, 2020 at 05:11:18PM -0500, Scott Andrews wrote: > On 1/4/20 1:45 PM, Flareon Zulu wrote: >> On January 4, 2020, at 09:47, Scott Andrews >> wrote: >> >>> Anyone have this error? >>> ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o >>> m-regex.o mbrlen.o regex.o >>> ranlib libgrep.a >>> make[3]: Leaving directory >>> '/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep' >>> Making all in src >>> here=`pwd`; \ >>> cd ../../libtextstyle/lib && \ >>> /usr/bin/make install-nobase_includeHEADERS >>> install-nobase_nodist_includeHEADERS includedir="$here" >>> make[3]: *** No rule to make target 'install-nobase_includeHEADERS'. >> Stop. >>> make[2]: *** [Makefile:3955: textstyle.h] Error 2 >>> make[1]: *** [Makefile:2173: all-recursive] Error 1 >>> make: *** [Makefile:2041: all] Error 2 >>> Didn't see anything on the list about this >>> Gettext-0.19.8.1 is ok >>> -- >> Especially in light of this: https://savannah.gnu.org/bugs/?56333 >> >> It seems there could be an issue with build order, essentially. I didn't >> have an issue, but some people online have had this happen, they're just >> not on this list. >> >> Flareon Zulu >> > Could very well be, I will follow up on the link you posted and see if I > caqn make sense in it. > > The usual workaround for what that sounds like is "make -j1". Apologies if you are already doing that. My most recent example of that was in bison on a Skylake (an i3 so I'd been running make -j4 : perhaps -j3 or -j2 might have sufficed). On other machines (haswell i7, ryzen 3400G) make -j8 was fine. Modern CPUs can be a pain. And that is another thing to learn from LFS - ISTR that dropping back to -j1 in case of problems is mentioned in the FAQ. >>> In section 4.5. About SBUs, the last sentence in the note: >>> >>> "If you run into a problem with a build step, revert back to a single >>> processor build to properly analyze the error messages." >>> >>> This may be the cause of the error, but I think it is unlikely. The last >>> release of gettext was in May and we certainly would have run into the >>> problem >>> before this if it has a race condition. >>> >> Hmmm, in our automated build (jhalfs), gettext used to be blacklisted for >> optimizations (means it was compiled with make -j1), until December 21st, >> when >> I've removed blacklist in jhalfs. I've built several times since then at -j8 >> on a Haswell, so gettext can be compilled at -j8 on that CPU, but maybe, as >> Ken mentioned, modern CPU's could do something different... If there is more >> evidence that there is a race condition in gettext, I'll blacklist it again. >> >> Pierre >This is what I used in the build: >./configure --disable-shared >make -j1 >The result: >rm -f libgrep.a >ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o >m-regex.o mbrlen.o regex.o >ranlib libgrep.a >make[3]: Leaving directory >'/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep' >make[2]: Leaving directory >'/mnt/lfs/source/BUILD/gettext-0.20.1/gettext-tools/libgrep' >Making all in src >make[2]: Entering directory >'/mnt/lfs/source/gettext-0.20.1/gettext-tools/src' >here=`pwd`; \ >cd ../../libtextstyle/lib && \ > make install-nobase_includeHEADERS >install-nobase_nodist_includeHEADERS includedir="$here" >make[3]: Entering directory >'/mnt/lfs/usr/src/LFS-RPi/BUILD/gettext-0.20.1/libtextstyle/lib' >make[3]: *** No rule to make target 'install-nobase_includeHEADERS'. Stop. >make[3]: Leaving directory >'/mnt/lfs/usr/src/LFS-RPi/BUILD/gettext-0.20.1/libtextstyle/lib' >make[2]: *** [Makefile:3955: textstyle.h] Error 2 >make[2]: Leaving directory >'/mnt/lfs/usr/src/LFS-RPi/BUILD/gettext-0.20.1/gettext-tools/src' >make[1]: *** [Makefile:2173: all-recursive] Error 1 >make[1]: Leaving directory >'/mnt/lfs/usr/src/LFS-RPi/BUILD/gettext-0.20.1/gettext-tools' >make: *** [Makefile:2041: all] Error 2 >-- >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 My next suggestion in this saga is to try plain "make" if you didn't already. Otherwise, I'm stumped. Could we bug upstream about this? Flareon-- 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
Re: [lfs-support] LFS-9.0 5.24. Gettext-0.20.1 build error
On 1/5/20 8:01 AM, Scott Andrews wrote: This is what I used in the build: ./configure --disable-shared make -j1 The result: [snip] make[2]: Entering directory '/mnt/lfs/source/gettext-0.20.1/gettext-tools/src' here=`pwd`; \ cd ../../libtextstyle/lib && \ make install-nobase_includeHEADERS install-nobase_nodist_includeHEADERS includedir="$here" make[3]: Entering directory '/mnt/lfs/usr/src/LFS-RPi/BUILD/gettext-0.20.1/libtextstyle/lib' make[3]: *** No rule to make target 'install-nobase_includeHEADERS'. Stop. I'm not sure what is happening here. This is what I have in the same area: cd ../../libtextstyle/lib && \ make install-nobase_includeHEADERS install-nobase_nodist_includeHEADERS includedir="$here" make[6]: Entering directory '/mnt/lfs/sources/gettext-0.20.1/libtextstyle/lib' /tools/bin/mkdir -p '/mnt/lfs/sources/gettext-0.20.1/gettext-tools/src' /tools/bin/install -c -m 644 textstyle.h '/mnt/lfs/sources/gettext-0.20.1/gettext-tools/src/.' /tools/bin/mkdir -p '/mnt/lfs/sources/gettext-0.20.1/gettext-tools/src' /tools/bin/mkdir -p '/mnt/lfs/sources/gettext-0.20.1/gettext-tools/src/textstyle' ... What I do see in your log is Entering directory '/mnt/lfs/usr/src/LFS-RPi/BUILD... So the system is a Raspberry Pi? I'm wondering why you have: Entering /mnt/lfs/source/gettext-0.20.1/gettext-tools/src followed by Entering /mnt/lfs/usr/src/LFS-RPi/BUILD/... -- Bruce -- 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-9.0 5.24. Gettext-0.20.1 build error
On 1/5/20 3:35 AM, Pierre Labastie wrote: Le 05/01/2020 à 05:37, Bruce Dubbs a écrit : On 1/4/20 7:45 PM, Ken Moffat wrote: On Sat, Jan 04, 2020 at 05:11:18PM -0500, Scott Andrews wrote: On 1/4/20 1:45 PM, Flareon Zulu wrote: On January 4, 2020, at 09:47, Scott Andrews wrote: Anyone have this error? ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o m-regex.o mbrlen.o regex.o ranlib libgrep.a make[3]: Leaving directory '/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep' Making all in src here=`pwd`; \ cd ../../libtextstyle/lib && \ /usr/bin/make install-nobase_includeHEADERS install-nobase_nodist_includeHEADERS includedir="$here" make[3]: *** No rule to make target 'install-nobase_includeHEADERS'. Stop. make[2]: *** [Makefile:3955: textstyle.h] Error 2 make[1]: *** [Makefile:2173: all-recursive] Error 1 make: *** [Makefile:2041: all] Error 2 Didn't see anything on the list about this Gettext-0.19.8.1 is ok -- Especially in light of this: https://savannah.gnu.org/bugs/?56333 It seems there could be an issue with build order, essentially. I didn't have an issue, but some people online have had this happen, they're just not on this list. Flareon Zulu Could very well be, I will follow up on the link you posted and see if I caqn make sense in it. The usual workaround for what that sounds like is "make -j1". Apologies if you are already doing that. My most recent example of that was in bison on a Skylake (an i3 so I'd been running make -j4 : perhaps -j3 or -j2 might have sufficed). On other machines (haswell i7, ryzen 3400G) make -j8 was fine. Modern CPUs can be a pain. And that is another thing to learn from LFS - ISTR that dropping back to -j1 in case of problems is mentioned in the FAQ. In section 4.5. About SBUs, the last sentence in the note: "If you run into a problem with a build step, revert back to a single processor build to properly analyze the error messages." This may be the cause of the error, but I think it is unlikely. The last release of gettext was in May and we certainly would have run into the problem before this if it has a race condition. Hmmm, in our automated build (jhalfs), gettext used to be blacklisted for optimizations (means it was compiled with make -j1), until December 21st, when I've removed blacklist in jhalfs. I've built several times since then at -j8 on a Haswell, so gettext can be compilled at -j8 on that CPU, but maybe, as Ken mentioned, modern CPU's could do something different... If there is more evidence that there is a race condition in gettext, I'll blacklist it again. Pierre This is what I used in the build: ./configure --disable-shared make -j1 The result: rm -f libgrep.a ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o m-regex.o mbrlen.o regex.o ranlib libgrep.a make[3]: Leaving directory '/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep' make[2]: Leaving directory '/mnt/lfs/source/BUILD/gettext-0.20.1/gettext-tools/libgrep' Making all in src make[2]: Entering directory '/mnt/lfs/source/gettext-0.20.1/gettext-tools/src' here=`pwd`; \ cd ../../libtextstyle/lib && \ make install-nobase_includeHEADERS install-nobase_nodist_includeHEADERS includedir="$here" make[3]: Entering directory '/mnt/lfs/usr/src/LFS-RPi/BUILD/gettext-0.20.1/libtextstyle/lib' make[3]: *** No rule to make target 'install-nobase_includeHEADERS'. Stop. make[3]: Leaving directory '/mnt/lfs/usr/src/LFS-RPi/BUILD/gettext-0.20.1/libtextstyle/lib' make[2]: *** [Makefile:3955: textstyle.h] Error 2 make[2]: Leaving directory '/mnt/lfs/usr/src/LFS-RPi/BUILD/gettext-0.20.1/gettext-tools/src' make[1]: *** [Makefile:2173: all-recursive] Error 1 make[1]: Leaving directory '/mnt/lfs/usr/src/LFS-RPi/BUILD/gettext-0.20.1/gettext-tools' make: *** [Makefile:2041: all] Error 2 -- 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-9.0 5.24. Gettext-0.20.1 build error
On 1/4/20 7:38 PM, Bruce Dubbs wrote: On 1/4/20 4:11 PM, Scott Andrews wrote: On 1/4/20 1:45 PM, Flareon Zulu wrote: On January 4, 2020, at 09:47, Scott Andrews wrote: >Anyone have this error? >ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o >m-regex.o mbrlen.o regex.o >ranlib libgrep.a >make[3]: Leaving directory >'/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep' >Making all in src >here=`pwd`; \ >cd ../../libtextstyle/lib && \ > /usr/bin/make install-nobase_includeHEADERS >install-nobase_nodist_includeHEADERS includedir="$here" >make[3]: *** No rule to make target 'install-nobase_includeHEADERS'. Stop. >make[2]: *** [Makefile:3955: textstyle.h] Error 2 >make[1]: *** [Makefile:2173: all-recursive] Error 1 >make: *** [Makefile:2041: all] Error 2 >Didn't see anything on the list about this >Gettext-0.19.8.1 is ok >-- >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 Especially in light of this: https://savannah.gnu.org/bugs/?56333 It seems there could be an issue with build order, essentially. I didn't have an issue, but some people online have had this happen, they're just not on this list. Flareon Zulu Could very well be, I will follow up on the link you posted and see if I caqn make sense in it. It is doubtful that the problem is build order. Most of the time when we update packages we do a complete rebuild of all LFS packages by extracting the instructions from the xml source. Th eprocess is completely automated and errors will show up then. Since the problem is in Chapter 5, there are really only two possibilities: an error when following previous instructions or a problem with the host system. -- Bruce The host system is LFS-8.4 that has been running since version 8.4 came out. The p.0 version I am building is using the exact same scripts to build it as I used in the 8.4 build. I went through the book chapter/section by section making the changes beteeewn version 8.4 to version 9.0. Then started the build. All of chapter 5 built with the exception of gettext-0.2.1, reverting to the previous version of gettext built and all of chapter 5 built. -- 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-9.0 5.24. Gettext-0.20.1 build error
Le 05/01/2020 à 05:37, Bruce Dubbs a écrit : > On 1/4/20 7:45 PM, Ken Moffat wrote: >> On Sat, Jan 04, 2020 at 05:11:18PM -0500, Scott Andrews wrote: >>> >>> On 1/4/20 1:45 PM, Flareon Zulu wrote: On January 4, 2020, at 09:47, Scott Andrews wrote: > Anyone have this error? > ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o > m-regex.o mbrlen.o regex.o > ranlib libgrep.a > make[3]: Leaving directory > '/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep' > Making all in src > here=`pwd`; \ > cd ../../libtextstyle/lib && \ > /usr/bin/make install-nobase_includeHEADERS > install-nobase_nodist_includeHEADERS includedir="$here" > make[3]: *** No rule to make target 'install-nobase_includeHEADERS'. Stop. > make[2]: *** [Makefile:3955: textstyle.h] Error 2 > make[1]: *** [Makefile:2173: all-recursive] Error 1 > make: *** [Makefile:2041: all] Error 2 > Didn't see anything on the list about this > Gettext-0.19.8.1 is ok > -- >> Especially in light of this: https://savannah.gnu.org/bugs/?56333 It seems there could be an issue with build order, essentially. I didn't have an issue, but some people online have had this happen, they're just not on this list. Flareon Zulu >>> Could very well be, I will follow up on the link you posted and see if I >>> caqn make sense in it. >>> >>> >> The usual workaround for what that sounds like is "make -j1". >> Apologies if you are already doing that. My most recent example of >> that was in bison on a Skylake (an i3 so I'd been running make -j4 : >> perhaps -j3 or -j2 might have sufficed). On other machines (haswell >> i7, ryzen 3400G) make -j8 was fine. Modern CPUs can be a pain. >> >> And that is another thing to learn from LFS - ISTR that dropping >> back to -j1 in case of problems is mentioned in the FAQ. > > In section 4.5. About SBUs, the last sentence in the note: > > "If you run into a problem with a build step, revert back to a single > processor build to properly analyze the error messages." > > This may be the cause of the error, but I think it is unlikely. The last > release of gettext was in May and we certainly would have run into the problem > before this if it has a race condition. > Hmmm, in our automated build (jhalfs), gettext used to be blacklisted for optimizations (means it was compiled with make -j1), until December 21st, when I've removed blacklist in jhalfs. I've built several times since then at -j8 on a Haswell, so gettext can be compilled at -j8 on that CPU, but maybe, as Ken mentioned, modern CPU's could do something different... If there is more evidence that there is a race condition in gettext, I'll blacklist it again. 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
Re: [lfs-support] LFS-9.0 5.24. Gettext-0.20.1 build error
On 1/4/20 7:45 PM, Ken Moffat wrote: On Sat, Jan 04, 2020 at 05:11:18PM -0500, Scott Andrews wrote: On 1/4/20 1:45 PM, Flareon Zulu wrote: On January 4, 2020, at 09:47, Scott Andrews wrote: Anyone have this error? ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o m-regex.o mbrlen.o regex.o ranlib libgrep.a make[3]: Leaving directory '/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep' Making all in src here=`pwd`; \ cd ../../libtextstyle/lib && \ /usr/bin/make install-nobase_includeHEADERS install-nobase_nodist_includeHEADERS includedir="$here" make[3]: *** No rule to make target 'install-nobase_includeHEADERS'. Stop. make[2]: *** [Makefile:3955: textstyle.h] Error 2 make[1]: *** [Makefile:2173: all-recursive] Error 1 make: *** [Makefile:2041: all] Error 2 Didn't see anything on the list about this Gettext-0.19.8.1 is ok -- Especially in light of this: https://savannah.gnu.org/bugs/?56333 It seems there could be an issue with build order, essentially. I didn't have an issue, but some people online have had this happen, they're just not on this list. Flareon Zulu Could very well be, I will follow up on the link you posted and see if I caqn make sense in it. The usual workaround for what that sounds like is "make -j1". Apologies if you are already doing that. My most recent example of that was in bison on a Skylake (an i3 so I'd been running make -j4 : perhaps -j3 or -j2 might have sufficed). On other machines (haswell i7, ryzen 3400G) make -j8 was fine. Modern CPUs can be a pain. And that is another thing to learn from LFS - ISTR that dropping back to -j1 in case of problems is mentioned in the FAQ. In section 4.5. About SBUs, the last sentence in the note: "If you run into a problem with a build step, revert back to a single processor build to properly analyze the error messages." This may be the cause of the error, but I think it is unlikely. The last release of gettext was in May and we certainly would have run into the problem before this if it has a race condition. -- Bruce . -- 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-9.0 5.24. Gettext-0.20.1 build error
On Sat, Jan 04, 2020 at 05:11:18PM -0500, Scott Andrews wrote: > > On 1/4/20 1:45 PM, Flareon Zulu wrote: > > > > On January 4, 2020, at 09:47, Scott Andrews > > wrote: > > > > >Anyone have this error? > > >ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o > > >m-regex.o mbrlen.o regex.o > > >ranlib libgrep.a > > >make[3]: Leaving directory > > >'/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep' > > >Making all in src > > >here=`pwd`; \ > > >cd ../../libtextstyle/lib && \ > > > /usr/bin/make install-nobase_includeHEADERS > > >install-nobase_nodist_includeHEADERS includedir="$here" > > >make[3]: *** No rule to make target 'install-nobase_includeHEADERS'. > > Stop. > > >make[2]: *** [Makefile:3955: textstyle.h] Error 2 > > >make[1]: *** [Makefile:2173: all-recursive] Error 1 > > >make: *** [Makefile:2041: all] Error 2 > > >Didn't see anything on the list about this > > >Gettext-0.19.8.1 is ok > > >-- > > > > Especially in light of this: https://savannah.gnu.org/bugs/?56333 > > > > It seems there could be an issue with build order, essentially. I didn't > > have an issue, but some people online have had this happen, they're just > > not on this list. > > > > Flareon Zulu > > > Could very well be, I will follow up on the link you posted and see if I > caqn make sense in it. > > The usual workaround for what that sounds like is "make -j1". Apologies if you are already doing that. My most recent example of that was in bison on a Skylake (an i3 so I'd been running make -j4 : perhaps -j3 or -j2 might have sufficed). On other machines (haswell i7, ryzen 3400G) make -j8 was fine. Modern CPUs can be a pain. And that is another thing to learn from LFS - ISTR that dropping back to -j1 in case of problems is mentioned in the FAQ. ĸen -- The right of the people to keep and arm Bears, shall not be infringed. -- 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-9.0 5.24. Gettext-0.20.1 build error
On 1/4/20 4:11 PM, Scott Andrews wrote: On 1/4/20 1:45 PM, Flareon Zulu wrote: On January 4, 2020, at 09:47, Scott Andrews wrote: >Anyone have this error? >ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o >m-regex.o mbrlen.o regex.o >ranlib libgrep.a >make[3]: Leaving directory >'/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep' >Making all in src >here=`pwd`; \ >cd ../../libtextstyle/lib && \ > /usr/bin/make install-nobase_includeHEADERS >install-nobase_nodist_includeHEADERS includedir="$here" >make[3]: *** No rule to make target 'install-nobase_includeHEADERS'. Stop. >make[2]: *** [Makefile:3955: textstyle.h] Error 2 >make[1]: *** [Makefile:2173: all-recursive] Error 1 >make: *** [Makefile:2041: all] Error 2 >Didn't see anything on the list about this >Gettext-0.19.8.1 is ok >-- >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 Especially in light of this: https://savannah.gnu.org/bugs/?56333 It seems there could be an issue with build order, essentially. I didn't have an issue, but some people online have had this happen, they're just not on this list. Flareon Zulu Could very well be, I will follow up on the link you posted and see if I caqn make sense in it. It is doubtful that the problem is build order. Most of the time when we update packages we do a complete rebuild of all LFS packages by extracting the instructions from the xml source. Th eprocess is completely automated and errors will show up then. Since the problem is in Chapter 5, there are really only two possibilities: an error when following previous instructions or a problem with the host system. -- Bruce -- 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-9.0 5.24. Gettext-0.20.1 build error
On 1/4/20 1:45 PM, Flareon Zulu wrote: On January 4, 2020, at 09:47, Scott Andrews wrote: >Anyone have this error? >ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o >m-regex.o mbrlen.o regex.o >ranlib libgrep.a >make[3]: Leaving directory >'/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep' >Making all in src >here=`pwd`; \ >cd ../../libtextstyle/lib && \ > /usr/bin/make install-nobase_includeHEADERS >install-nobase_nodist_includeHEADERS includedir="$here" >make[3]: *** No rule to make target 'install-nobase_includeHEADERS'. Stop. >make[2]: *** [Makefile:3955: textstyle.h] Error 2 >make[1]: *** [Makefile:2173: all-recursive] Error 1 >make: *** [Makefile:2041: all] Error 2 >Didn't see anything on the list about this >Gettext-0.19.8.1 is ok >-- >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 Especially in light of this: https://savannah.gnu.org/bugs/?56333 It seems there could be an issue with build order, essentially. I didn't have an issue, but some people online have had this happen, they're just not on this list. Flareon Zulu Could very well be, I will follow up on the link you posted and see if I caqn make sense in it. Thanks -- 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-9.0 5.24. Gettext-0.20.1 build error
On 1/4/20 1:38 PM, Flareon Zulu wrote: On January 4, 2020, at 09:47, Scott Andrews wrote: >Anyone have this error? >ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o >m-regex.o mbrlen.o regex.o >ranlib libgrep.a >make[3]: Leaving directory >'/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep' >Making all in src >here=`pwd`; \ >cd ../../libtextstyle/lib && \ > /usr/bin/make install-nobase_includeHEADERS >install-nobase_nodist_includeHEADERS includedir="$here" >make[3]: *** No rule to make target 'install-nobase_includeHEADERS'. Stop. >make[2]: *** [Makefile:3955: textstyle.h] Error 2 >make[1]: *** [Makefile:2173: all-recursive] Error 1 >make: *** [Makefile:2041: all] Error 2 >Didn't see anything on the list about this >Gettext-0.19.8.1 is ok >-- >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 What was the command this failed on? I didn't get it before when I was compiling my base or my main systems. Also, were you testing anything else on the package? That might be a place to start looking, cause I'm curious now. Flareon Zulu The make command after the configure ran Never got to make install -- 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-9.0 5.24. Gettext-0.20.1 build error
On January 4, 2020, at 09:47, Scott Andrews wrote: >Anyone have this error? >ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o >m-regex.o mbrlen.o regex.o >ranlib libgrep.a >make[3]: Leaving directory >'/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep' >Making all in src >here=`pwd`; \ >cd ../../libtextstyle/lib && \ > /usr/bin/make install-nobase_includeHEADERS >install-nobase_nodist_includeHEADERS includedir="$here" >make[3]: *** No rule to make target 'install-nobase_includeHEADERS'. Stop. >make[2]: *** [Makefile:3955: textstyle.h] Error 2 >make[1]: *** [Makefile:2173: all-recursive] Error 1 >make: *** [Makefile:2041: all] Error 2 >Didn't see anything on the list about this >Gettext-0.19.8.1 is ok >-- >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 Especially in light of this: https://savannah.gnu.org/bugs/?56333 It seems there could be an issue with build order, essentially. I didn't have an issue, but some people online have had this happen, they're just not on this list. Flareon Zulu-- 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-9.0 5.24. Gettext-0.20.1 build error
On January 4, 2020, at 09:47, Scott Andrews wrote: >Anyone have this error? >ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o >m-regex.o mbrlen.o regex.o >ranlib libgrep.a >make[3]: Leaving directory >'/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep' >Making all in src >here=`pwd`; \ >cd ../../libtextstyle/lib && \ > /usr/bin/make install-nobase_includeHEADERS >install-nobase_nodist_includeHEADERS includedir="$here" >make[3]: *** No rule to make target 'install-nobase_includeHEADERS'. Stop. >make[2]: *** [Makefile:3955: textstyle.h] Error 2 >make[1]: *** [Makefile:2173: all-recurs ive] Error 1 >make: *** [Makefile:2041: all] Error 2 >Didn't see anything on the list about this >Gettext-0.19.8.1 is ok >-- >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 What was the command this failed on? I didn't get it before when I was compiling my base or my main systems. Also, were you testing anything else on the package? That might be a place to start looking, cause I'm curious now. Flareon Zulu-- 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
