On Tuesday 10 January 2006 5:01 pm, [EMAIL PROTECTED] wrote: > Send lfs-support mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://linuxfromscratch.org/mailman/listinfo/lfs-support > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of lfs-support digest..." > > > Today's Topics: > > 1. Re: lfs AMD64 (Matt Darcy) > 2. Re: Tests fail (Hardik Mehta) > 3. Wireless Help in SVN20060103 (James Henry) > 4. compiling Glibc-2.3.4 LFS 6.1 Host Debian 3.1 did fail > (Clemens HAUPT) > 5. Re: compiling Glibc-2.3.4 LFS 6.1 Host Debian 3.1 did fail > (Dan Nicholson) > 6. Re: compiling Glibc-2.3.4 LFS 6.1 Host Debian 3.1 did fail > (Clemens HAUPT) > 7. Re: compiling Glibc-2.3.4 LFS 6.1 Host Debian 3.1 did fail > (Jeremy Huntwork) > 8. Building glibc in section 5.6 (was: compiling Glibc-2.3.4 LFS > 6.1 Host Debian 3.1 did fail) (Clemens HAUPT) > 9. Re: compiling Glibc-2.3.4 LFS 6.1 Host Debian 3.1 did fail > (Dan Nicholson) > 10. Re: compiling Glibc-2.3.4 LFS 6.1 Host Debian 3.1 did fail > (Clemens HAUPT) > 11. Re: Building glibc in section 5.6 (was: compiling Glibc-2.3.4 > LFS 6.1 Host Debian 3.1 did fail) (Dan Nicholson) > 12. Re: Building glibc in section 5.6 (was: compiling Glibc-2.3.4 > LFS 6.1 Host Debian 3.1 did fail) (Clemens HAUPT) > 13. Re: Building glibc in section 5.6 (Jeremy Huntwork) > 14. Re: Building glibc in section 5.6 (was: compiling Glibc-2.3.4 > LFS 6.1 Host Debian 3.1 did fail) (Dan Nicholson) > 15. Re: Building glibc in section 5.6 (was: compiling Glibc-2.3.4 > LFS 6.1 Host Debian 3.1 did fail) (Clemens HAUPT) > 16. Re: Building glibc in section 5.6 (Clemens HAUPT) > 17. Re: Building glibc in section 5.6 (was: compiling Glibc-2.3.4 > LFS 6.1 Host Debian 3.1 did fail) (Clemens HAUPT) > 18. Re: Building glibc in section 5.6 (John Benes) > 19. Re: Building glibc in section 5.6 (was: compiling Glibc-2.3.4 > LFS 6.1 Host Debian 3.1 did fail) (Dan Nicholson) > 20. Re: Building glibc in section 5.6 (was: compiling Glibc-2.3.4 > LFS 6.1 Host Debian 3.1 did fail) (Clemens HAUPT) > 21. Re: Building glibc in section 5.6 (Clemens HAUPT) > 22. Re: Building glibc in section 5.6 (Chris Staub) > 23. Re: Building glibc in section 5.6 (Jeremy Huntwork) > 24. gcc error (tcp) > 25. Re: gcc error (Jeremy Huntwork) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 09 Jan 2006 11:09:52 +0000 > From: Matt Darcy <[EMAIL PROTECTED]> > Subject: Re: lfs AMD64 > To: LFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > IraqiGeek wrote: > > On Sunday, January 08, 2006 2:07 PM GMT, > > > > i040866 <[EMAIL PROTECTED]> wrote: > >> Hi Everyone. > >> > >> I have a doubt. I have a AMD Turion 64 MT, and I want to install a > >> linux from scratch on in, but I do not know if I should use asm-i386 > >> linux libc headers, > >> or asm-x86_64. When I do uname I get, among other things, i386 and > >> i686. By > >> this I guess I should use asm-i386, but I'm not sure of the > >> implications of this. > >> > >> So, if you could _please_ help me with this, it would be great. > >> > >> Thanks in advance! > > > > For the best possible performance in 32-bit mode, use i686. If you want > > to natively run everything in 64bit mode, use x86_64. For the sake of > > backwards compatibility, I suggest you use i686. > > > > Regards, > > IraqiGeek > > www.iraqigeek.com > > This is nonsense. > > At present you cannot build an AMD64 LFS system usig the LFS book. so > please do not use the x86_64 headers as iraqigeeks suggests - your > system will fail. > > The only way to build a 64bit system is to cross-build one at present, > which has problems due to not least the lack of 64bit bootloaders, and > the 32bit dependencies of 32bit boot loaders. > > Take a look at the cross-lfs project for more details on this. > > Matt > > > > > > ------------------------------ > > Message: 2 > Date: Mon, 9 Jan 2006 04:14:49 -0800 (PST) > From: Hardik Mehta <[EMAIL PROTECTED]> > Subject: Re: Tests fail > To: LFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=iso-8859-1 > > Hi, > > this is the same error I was getting and I had > problems with PERL > > the details can be see at ... > > http://www.linuxquestions.org/questions/showthread.php?t=397206 > > try running the test .. perhaps you will only need to > rename some files .. > > Hardik. > > > --- "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > > wrote: > > I put the 6.8 repopulation in root's bash_profile in > > the chroot environment, replaced the glibc source, > > and tried once more. It wasn't successful. I ran a > > log of the make check, and grepped it for "Error" to > > get this: > > > > make[2]: *** > > [/usr/local/src/glibc-build/libio/tst-fopenloc.check] > > > Error 127 > > make[1]: *** [libio/tests] Error 2 > > make[2]: *** > > [/usr/local/src/glibc-build/posix/bug-regex24.out] > > Error 1 > > make[2]: *** > > [/usr/local/src/glibc-build/posix/tst-regex2.out] > > Error 1 > > make[2]: > > [/usr/local/src/glibc-build/posix/annexc.out] Error > > 1 (ignored) > > make[2]: *** > > [/usr/local/src/glibc-build/posix/bug-regex2-mem] > > Error 127 > > make[2]: *** > > [/usr/local/src/glibc-build/posix/bug-regex14-mem] > > Error 127 > > make[2]: *** > > [/usr/local/src/glibc-build/posix/bug-regex21-mem] > > Error 127 > > make[2]: *** > > [/usr/local/src/glibc-build/posix/tst-rxspencer-mem] > > Error 127 > > make[2]: *** > > [/usr/local/src/glibc-build/posix/tst-pcre-mem] > > Error 127 > > make[2]: *** > > [/usr/local/src/glibc-build/posix/tst-boost-mem] > > Error 127 > > make[2]: *** > > [/usr/local/src/glibc-build/posix/bug-glob2-mem] > > Error 127 > > make[1]: *** [posix/tests] Error 2 > > make[2]: *** > > [/usr/local/src/glibc-build/nptl/tst-stack3-mem] > > Error 127 > > make[1]: *** [nptl/tests] Error 2 > > make: *** [check] Error 2 > > > > I suppose this means I need to start all over, Ch5 > > isn't correct? Blow it all away and rebuild Ch5 and > > run all the tests? Just Ch5's glibc Pass 2? GCC? > > How do I figure out what's usable, what isn't, and > > how to get back on track? > > > > I also read 7.4 and the referenced FAQ. It says: > > "Q: How will udev handle the /dev filesystem? > > A: /dev is recomended to be a tmpfs filesystem that > > is recreated on > > every reboot. Although, udev does not care what > > kind of filesystem > > it runs on." > > So my question is: Is there a reason I shouldn't > > build /dev in the root partition during the build > > process, then later let the udev bootscript build it > > in a tempfs? I could always rebuild /dev while the > > host system is running to the bare minimums of 6.8. > > Consider it's a given that not only will this build > > be done in many sessions, but there will be many > > power-off's, and many times I'll have to use the > > host for other purposes. > > > > > > > > Paul Rogers ([EMAIL PROTECTED]) > > http://www.xprt.net/~pgrogers/ > > Rogers' Second Law: "Everything you do > > communicates." > > (I do not personally endorse any additions after > > this line. TANSTAAFL :-) > > > > > > -- > > http://linuxfromscratch.org/mailman/listinfo/lfs-support > > > FAQ: http://www.linuxfromscratch.org/lfs/faq.html > > Unsubscribe: See the above information page > > __________________________________________ > Yahoo! DSL Something to write home about. > Just $16.99/mo. or less. > dsl.yahoo.com > > > ------------------------------ > > Message: 3 > Date: Mon, 09 Jan 2006 10:17:11 -0500 > From: James Henry <[EMAIL PROTECTED]> > Subject: Wireless Help in SVN20060103 > To: LFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > can anyone send me a good link to reseach how to set up my wireless card > in the LFS environment > > my ubuntu setup reports this from iwconfig: > > lo no wireless extensions. > > eth0 no wireless extensions. > > ra0 RT2500 Wireless ESSID:"NETGEAR" > Mode:Managed Frequency=2.412 GHz Access Point: > 00:09:5B:B0:94:D4 Bit Rate:11 Mb/s > RTS thr:off Fragment thr:off > Link Quality=80/100 Signal level=-69 dBm Noise level:-197 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > sit0 no wireless extensions. > > > im running on a AMD Athlon XP-M averatec laptop with kernel version > 2.5.16 using the same configuration as the ubuntu side > > my main question is setting up the device for my wireless card, this > card is an internal one with a disable button by the power button on the > laptop. this button does not seem to work, if i could get this to work > to turn on and off my connection would also be nice! > > --thanks James P. Henry > > ------------------------------ > > Message: 4 > Date: Mon, 9 Jan 2006 17:13:29 +0100 > From: Clemens HAUPT <[EMAIL PROTECTED]> > Subject: compiling Glibc-2.3.4 LFS 6.1 Host Debian 3.1 did fail > To: LFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > Sorry for inconvenience, > I don't want to disturb. > But! > If you are so kind to spend a little time for me, > please read the attachment and be sure of all my > thankfullness ;-) > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: glibc-build-desaster.bz2 > Type: application/x-bzip2 > Size: 1985 bytes > Desc: not available > Url : > http://linuxfromscratch.org/pipermail/lfs-support/attachments/20060109/a412 >df08/glibc-build-desaster-0001.bin > > ------------------------------ > > Message: 5 > Date: Mon, 9 Jan 2006 09:17:36 -0800 > From: Dan Nicholson <[EMAIL PROTECTED]> > Subject: Re: compiling Glibc-2.3.4 LFS 6.1 Host Debian 3.1 did fail > To: [EMAIL PROTECTED], LFS Support List > <[email protected]> > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > On 1/9/06, Clemens HAUPT <[EMAIL PROTECTED]> wrote: > > Sorry for inconvenience, > > No inconvenience. In the future, even if you're attaching a file, > please post the relevant error in the email so everyone knows what > they're dealing with. In your case, your building glibc in section > 5.6, and the error during the make command is: > > make -r PARALLELMFLAGS="" CVSOPTS="" -C ../glibc-2.3.4 objdir=`pwd` check > make[1]: Entering directory `/mnt/lfs/sources/glibc-2.3.4' > autoconf sysdeps/i386/elf/configure.in > sysdeps/i386/elf/configure.new > autoconf: Undefined macros: > ***BUG in Autoconf--please report*** AC_FD_MSG > make[1]: *** [sysdeps/i386/elf/configure] Error 1 > make[1]: Leaving directory `/mnt/lfs/sources/glibc-2.3.4' > make: *** [check] Error 2 > > I don't know if this will help, but DIY-Linux suppresses autoconf by > adding AUTOCONF=no to the make command. Try this instead of make: > > make AUTOCONF=no > > This can be seen here > http://www.diy-linux.org/x86-reference-build/temptools.html#tt-glibc > > Please let me know if this helps. If it does, this is a good addition > to the LFS book. > > -- > Dan > > ------------------------------ > > Message: 6 > Date: Mon, 9 Jan 2006 18:54:39 +0100 > From: Clemens HAUPT <[EMAIL PROTECTED]> > Subject: Re: compiling Glibc-2.3.4 LFS 6.1 Host Debian 3.1 did fail > To: LFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > While searching and seaching > I found that: > > Is it of any use? > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: glibc-build-desaster-II.bz2 > Type: application/x-bzip2 > Size: 1782 bytes > Desc: not available > Url : > http://linuxfromscratch.org/pipermail/lfs-support/attachments/20060109/5a9c >58e1/glibc-build-desaster-II-0001.bin > > ------------------------------ > > Message: 7 > Date: Mon, 09 Jan 2006 13:00:24 -0500 > From: Jeremy Huntwork <[EMAIL PROTECTED]> > Subject: Re: compiling Glibc-2.3.4 LFS 6.1 Host Debian 3.1 did fail > To: [EMAIL PROTECTED], LFS Support List > <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Clemens HAUPT wrote: > > While searching and seaching > > I found that: > > > > Is it of any use? > > Seriously, you'd get more support if you didn't use attachments, or if > you do, use non-compressed text attachments. > > -- > JH > > > ------------------------------ > > Message: 8 > Date: Mon, 9 Jan 2006 19:17:14 +0100 > From: Clemens HAUPT <[EMAIL PROTECTED]> > Subject: Building glibc in section 5.6 (was: compiling Glibc-2.3.4 LFS > 6.1 Host Debian 3.1 did fail) > To: LFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > >On 1/9/06, Clemens HAUPT <[EMAIL PROTECTED]> wrote: > >> Sorry for inconvenience, > > > >No inconvenience. In the future, even if you're attaching a file, > >please post the relevant error in the email so everyone knows what > >they're dealing with. > > Thank you so much for your hint > > >In your case, your building glibc in section > >5.6, and the error during the make command is: > > > >make -r PARALLELMFLAGS="" CVSOPTS="" -C ../glibc-2.3.4 objdir=`pwd` check > >make[1]: Entering directory `/mnt/lfs/sources/glibc-2.3.4' > >autoconf sysdeps/i386/elf/configure.in > sysdeps/i386/elf/configure.new > >autoconf: Undefined macros: > >***BUG in Autoconf--please report*** AC_FD_MSG > >make[1]: *** [sysdeps/i386/elf/configure] Error 1 > >make[1]: Leaving directory `/mnt/lfs/sources/glibc-2.3.4' > >make: *** [check] Error 2 > > Absolutly right. > > >I don't know if this will help, but DIY-Linux suppresses autoconf by > >adding AUTOCONF=no to the make command. Try this instead of make: > > > >make AUTOCONF=no > > Done. STARTED! It started working absolutly mad! ;-) > > >This can be seen here > >http://www.diy-linux.org/x86-reference-build/temptools.html#tt-glibc > > OH! What's that! Amazing! > > >Please let me know if this helps. If it does, this is a good addition > >to the LFS book. > > Well, it started and it's running and running and running.... > Let me answer in about 3 hours from now on ;-) (nearly 11.8 SBU!) > ;-) > > I am deeply impressed to possibly make a tribute to the LFS-Bible ;-) > > -- > Bitte senden Sie mir keine Word-, HTML- oder PowerPoint-Anhänge. > Siehe http://www.gnu.org/philosophy/no-word-attachments.de.html > > ------------------------------ > > Message: 9 > Date: Mon, 9 Jan 2006 10:21:10 -0800 > From: Dan Nicholson <[EMAIL PROTECTED]> > Subject: Re: compiling Glibc-2.3.4 LFS 6.1 Host Debian 3.1 did fail > To: [EMAIL PROTECTED], LFS Support List > <[email protected]> > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > On 1/9/06, Clemens HAUPT <[EMAIL PROTECTED]> wrote: > > While searching and seaching > > I found that: > > > > Is it of any use? > > I have no idea. > > 1. Did you try what I suggested: "make AUTOCONF=no" ? > > 2. You may need autoconf-2.5.9 for this to work otherwise. What's > the output of "autoconf --version" ? > > -- > Dan > > ------------------------------ > > Message: 10 > Date: Mon, 9 Jan 2006 19:27:22 +0100 > From: Clemens HAUPT <[EMAIL PROTECTED]> > Subject: Re: compiling Glibc-2.3.4 LFS 6.1 Host Debian 3.1 did fail > To: LFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > Am Monday 09 January 2006 19:00 schrieben Sie: > >Clemens HAUPT wrote: > >> While searching and seaching > >> I found that: > >> > >> Is it of any use? > > > >Seriously, you'd get more support if you didn't use attachments, or if > >you do, use non-compressed text attachments. > > OH! > I beg your pardon! > I'm used to do so for those using Dial On Demand. > I happen to get already an extremly good hint. > > >From Dan Nicholson and compiling started fantastic. > > The machine is really working hard ;-) > I like looking at hard working machines while eating pizza;-) > -- > Bitte senden Sie mir keine Word-, HTML- oder PowerPoint-Anhänge. > Siehe http://www.gnu.org/philosophy/no-word-attachments.de.html > > ------------------------------ > > Message: 11 > Date: Mon, 9 Jan 2006 10:37:45 -0800 > From: Dan Nicholson <[EMAIL PROTECTED]> > Subject: Re: Building glibc in section 5.6 (was: compiling Glibc-2.3.4 > LFS 6.1 Host Debian 3.1 did fail) > To: [EMAIL PROTECTED], LFS Support List > <[email protected]> > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > On 1/9/06, Clemens HAUPT <[EMAIL PROTECTED]> wrote: > > >make AUTOCONF=no > > > > Done. STARTED! It started working absolutly mad! ;-) > > Clemens, > > Could you please tell me the output of > > autoconf --version > > That would help determine where the problem is. > > -- > Dan > > ------------------------------ > > Message: 12 > Date: Mon, 9 Jan 2006 21:33:27 +0100 > From: Clemens HAUPT <[EMAIL PROTECTED]> > Subject: Re: Building glibc in section 5.6 (was: compiling Glibc-2.3.4 > LFS 6.1 Host Debian 3.1 did fail) > To: LFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > Am Monday 09 January 2006 19:37 schrieben Sie: > >On 1/9/06, Clemens HAUPT <[EMAIL PROTECTED]> wrote: > >> >make AUTOCONF=no > >> > >> Done. STARTED! It started working absolutly mad! ;-) > > Sorry, is crazy the better word? > > >Clemens, > > > >Could you please tell me the output of > > > >autoconf --version > > It is: Autoconf version 2:13 > > >That would help determine where the problem is. > > Well. It worked absolutly perfect, but it stopped until that occured > > FATAL: kernel too old > make[2]: *** [/mnt/lfs/sources/glibc-build/sunrpc/xbootparam_prot.stmp] > Error 1 make[2]: Leaving directory `/mnt/lfs/sources/glibc-2.3.4/sunrpc' > make[1]: *** [sunrpc/others] Error 2 > make[1]: Leaving directory `/mnt/lfs/sources/glibc-2.3.4' > make: *** [all] Error 2 > > And now I don't know how to go on. If I can ignore that or what otherwise > can happen. I'll try to go on I think.... > > -- > Bitte senden Sie mir keine Word-, HTML- oder PowerPoint-Anhänge. > Siehe http://www.gnu.org/philosophy/no-word-attachments.de.html > > ------------------------------ > > Message: 13 > Date: Mon, 09 Jan 2006 15:36:59 -0500 > From: Jeremy Huntwork <[EMAIL PROTECTED]> > Subject: Re: Building glibc in section 5.6 > To: [EMAIL PROTECTED], LFS Support List > <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Clemens HAUPT wrote: > > FATAL: kernel too old > > make[2]: *** [/mnt/lfs/sources/glibc-build/sunrpc/xbootparam_prot.stmp] > > Error 1 make[2]: Leaving directory `/mnt/lfs/sources/glibc-2.3.4/sunrpc' > > make[1]: *** [sunrpc/others] Error 2 > > make[1]: Leaving directory `/mnt/lfs/sources/glibc-2.3.4' > > make: *** [all] Error 2 > > > > And now I don't know how to go on. If I can ignore that or what otherwise > > can happen. I'll try to go on I think.... > > What is the output of uname -r ? > > -- > JH > > ------------------------------ > > Message: 14 > Date: Mon, 9 Jan 2006 12:43:51 -0800 > From: Dan Nicholson <[EMAIL PROTECTED]> > Subject: Re: Building glibc in section 5.6 (was: compiling Glibc-2.3.4 > LFS 6.1 Host Debian 3.1 did fail) > To: [EMAIL PROTECTED], LFS Support List > <[email protected]> > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > On 1/9/06, Clemens HAUPT <[EMAIL PROTECTED]> wrote: > > >Could you please tell me the output of > > > > > >autoconf --version > > > > It is: Autoconf version 2:13 > > Thanks. I think glibc is using autoconf 2.59, and your autoconf is > incompatible. LFS shouldn't require that the host have this newer > autoconf, so this seems like a good fix. > > > FATAL: kernel too old > > make[2]: *** [/mnt/lfs/sources/glibc-build/sunrpc/xbootparam_prot.stmp] > > Error 1 make[2]: Leaving directory `/mnt/lfs/sources/glibc-2.3.4/sunrpc' > > make[1]: *** [sunrpc/others] Error 2 > > make[1]: Leaving directory `/mnt/lfs/sources/glibc-2.3.4' > > make: *** [all] Error 2 > > > > And now I don't know how to go on. If I can ignore that or what otherwise > > can happen. I'll try to go on I think.... > > Don't go on. Your glibc is not built. You'll fail later and have to > start over from here. > > What kernel are you running? Either enter "uname -r" or "cat > /proc/version". > > -- > Dan > > ------------------------------ > > Message: 15 > Date: Mon, 9 Jan 2006 22:48:05 +0100 > From: Clemens HAUPT <[EMAIL PROTECTED]> > Subject: Re: Building glibc in section 5.6 (was: compiling Glibc-2.3.4 > LFS 6.1 Host Debian 3.1 did fail) > To: LFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > Am Monday 09 January 2006 19:37 schrieben Sie: > > Hi Dan! > > Here is the personal protocol of what I did. > I did have to add AUTOCONF=no really several times > ___________________________________________ > > make check AUTOCONF=no > > FATAL: kernel too old > make[2]: *** [/mnt/lfs/sources/glibc-build/csu/tst-empty.out] Error 139 > make[2]: Leaving directory `/mnt/lfs/sources/glibc-2.3.4/csu' > make[1]: *** [csu/tests] Error 2 > make[1]: Leaving directory `/mnt/lfs/sources/glibc-2.3.4' > make: *** [check] Error 2 > > make -k check AUTOCONF=no > > much better. It's going on inspite of the too old Kernel. > Well the too old Kernel works fine anyway :->>> > Start several times! > (How often?) > mkdir /tools/etc > touch /tools/etc/ld.so.conf > make install AUTOCONF=no > make localedata/install-locales AUTOCONF=no > > going on tomorrow ;-) > If you don't mind :) > > > > -- > Bitte senden Sie mir keine Word-, HTML- oder PowerPoint-Anhänge. > Siehe http://www.gnu.org/philosophy/no-word-attachments.de.html > > ------------------------------ > > Message: 16 > Date: Mon, 9 Jan 2006 22:53:30 +0100 > From: Clemens HAUPT <[EMAIL PROTECTED]> > Subject: Re: Building glibc in section 5.6 > To: LFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > Am Monday 09 January 2006 21:36 schrieben Sie: > >> And now I don't know how to go on. If I can ignore that or what > >> otherwise can happen. I'll try to go on I think.... > > > >What is the output of uname -r ? > > uname -r > 2.4.18-bf2.4 > This is a debian 3.1 host > Of course it's quite old, but I have to start anyway > The hint make -k check overrules the often coming "Kernel too old" :->>> > I hope for I am just in section 5 it wil be enough to come to section 6 > finally :->>> -- > Bitte senden Sie mir keine Word-, HTML- oder PowerPoint-Anhänge. > Siehe http://www.gnu.org/philosophy/no-word-attachments.de.html > > ------------------------------ > > Message: 17 > Date: Mon, 9 Jan 2006 23:29:24 +0100 > From: Clemens HAUPT <[EMAIL PROTECTED]> > Subject: Re: Building glibc in section 5.6 (was: compiling Glibc-2.3.4 > LFS 6.1 Host Debian 3.1 did fail) > To: LFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > Am Monday 09 January 2006 21:43 schrieben Sie: > >On 1/9/06, Clemens HAUPT <[EMAIL PROTECTED]> wrote: > >> >Could you please tell me the output of > >> > > >> >autoconf --version > >> > >> It is: Autoconf version 2:13 > > > >Thanks. I think glibc is using autoconf 2.59, and your autoconf is > >incompatible. LFS shouldn't require that the host have this newer > >autoconf, so this seems like a good fix. > > OH! :-(((( > > >Don't go on. Your glibc is not built. You'll fail later and have to > >start over from here. > > I intend to say, I hate to read that. I will need at least five minutes to > overcome that. > > >What kernel are you running? Either enter "uname -r" or "cat > > /proc/version". > > Kernel 2.4.18-bf2.4 from debian 3.1 > gcc version 2.95.4 > Not good enough I'm afraid.... > > The only thing I else can present: > Kernel 2.6.1 > gcc version 2.95.4 > autoconf --version: autoconf (GNU Autoconf) 2.59 > as from Knoppix LiveCD. > would that work for me? > > I had a working LiveCD - bootable - from LFS 5, but for building > one of LFS6.1 I have to have kernel >2.6. > Please help from driving crazy :-[ > > -- > Bitte senden Sie mir keine Word-, HTML- oder PowerPoint-Anhänge. > Siehe http://www.gnu.org/philosophy/no-word-attachments.de.html > > ------------------------------ > > Message: 18 > Date: Mon, 09 Jan 2006 16:38:05 -0600 > From: John Benes <[EMAIL PROTECTED]> > Subject: Re: Building glibc in section 5.6 > To: [EMAIL PROTECTED], LFS Support List > <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > Clemens HAUPT wrote: > > I had a working LiveCD - bootable - from LFS 5, but for building > > > > one of LFS6.1 I have to have kernel >2.6. > > Please help from driving crazy :-[ > > There's a LiveCD made just for building LFS: > http://www.linuxfromscratch.org/livecd/ > > That CD should contain all of the correct versions of tools for you to > build LFS. > > -- > John Benes > GPG Fingerprint: D519 25DB BB5C 38FC 9D02 02E7 596D BC50 F880 27FA > "It is not only the living who are killed in war." - Isaac Asimov > > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 888 bytes > Desc: OpenPGP digital signature > Url : > http://linuxfromscratch.org/pipermail/lfs-support/attachments/20060109/905b >c831/signature-0001.bin > > ------------------------------ > > Message: 19 > Date: Mon, 9 Jan 2006 14:43:57 -0800 > From: Dan Nicholson <[EMAIL PROTECTED]> > Subject: Re: Building glibc in section 5.6 (was: compiling Glibc-2.3.4 > LFS 6.1 Host Debian 3.1 did fail) > To: [EMAIL PROTECTED], LFS Support List > <[email protected]> > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > On 1/9/06, Clemens HAUPT <[EMAIL PROTECTED]> wrote: > > >Don't go on. Your glibc is not built. You'll fail later and have to > > >start over from here. > > > > I intend to say, I hate to read that. I will need at least five minutes > > to overcome that. > > I may have been too harsh about the glibc build, but I think your > kernel is too old. > > > >What kernel are you running? Either enter "uname -r" or "cat > > > /proc/version". > > > > Kernel 2.4.18-bf2.4 from debian 3.1 > > gcc version 2.95.4 > > Not good enough I'm afraid.... > > I just looked on the debian website. It says that there is a 2.6.8 > kernel for debian 3.1. You could update to that. I don't know about > gcc, but LFS should bootstrap from 2.95, I think. > > > The only thing I else can present: > > Kernel 2.6.1 > > gcc version 2.95.4 > > autoconf --version: autoconf (GNU Autoconf) 2.59 > > as from Knoppix LiveCD. > > would that work for me? > > This would work. You could also download the LFS live cd. > http://www.linuxfromscratch.org/livecd/ > > You should be able to update your debian kernel without much pain. > You can still keep 2.4.18 for when you're using debian, but you > probably need 2.6 to build LFS. It's only temporary. > > > I had a working LiveCD - bootable - from LFS 5, but for building > > one of LFS6.1 I have to have kernel >2.6. > > Please help from driving crazy :-[ > > Sorry, you're gonna need kernel 2.6. > > -- > Dan > > ------------------------------ > > Message: 20 > Date: Tue, 10 Jan 2006 00:39:55 +0100 > From: Clemens HAUPT <[EMAIL PROTECTED]> > Subject: Re: Building glibc in section 5.6 (was: compiling Glibc-2.3.4 > LFS 6.1 Host Debian 3.1 did fail) > To: LFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > Am Monday 09 January 2006 23:43 schrieben Sie: > >I may have been too harsh about the glibc build, but I think your > >kernel is too old. > > Well thank you so much Dan for all your writing. > The Kernel I have works fine even being too old ;-) > > >I just looked on the debian website. It says that there is a 2.6.8 > >kernel for debian 3.1. You could update to that. I don't know about > >gcc, but LFS should bootstrap from 2.95, I think. > > That's it. Too old too (2 2s? :-) > > >> The only thing I else can present: > >> Kernel 2.6.1 > >> gcc version 2.95.4 > >> autoconf --version: autoconf (GNU Autoconf) 2.59 > >> as from Knoppix LiveCD. > >> would that work for me? > > > >This would work. You could also download the LFS live cd. > >http://www.linuxfromscratch.org/livecd/ > > I did it. But what for? For making a bootable CD I need a host > using Kernel 2.6 at least. With a machine with older Kernel the > liveCD and all the packages is not of any use. > > >You should be able to update your debian kernel without much pain. > >You can still keep 2.4.18 for when you're using debian, but you > >probably need 2.6 to build LFS. It's only temporary. > > Updating to 2.6.8 means downloading 10 CDs a newer version > as far as I can judge. > > >Sorry, you're gonna need kernel 2.6. > > I 've got it. > > -- > Bitte senden Sie mir keine Word-, HTML- oder PowerPoint-Anhänge. > Siehe http://www.gnu.org/philosophy/no-word-attachments.de.html > > ------------------------------ > > Message: 21 > Date: Tue, 10 Jan 2006 00:25:28 +0100 > From: Clemens HAUPT <[EMAIL PROTECTED]> > Subject: Re: Building glibc in section 5.6 > To: LFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > Am Monday 09 January 2006 23:38 schrieben Sie: > >> one of LFS6.1 I have to have kernel >2.6. > >> Please help from driving crazy :-[ > > > >There's a LiveCD made just for building LFS: > >http://www.linuxfromscratch.org/livecd/ > > Well, that's just the place where I did get all the files > > >That CD should contain all of the correct versions of tools for you to > >build LFS. > > Absolutly right. BUT! > You can't do anything with all this nice packages, they are all of > no use. One might present them to grandma, but neither oneself > nor grandma can do anything with it when you don't have > a LINUX Kernel not 2.6 on a single machine. > The liveCD in that place in not bootable. So if burnt on a CD > you can decorate your bicycle with it, nothing else. > I do have a bootable LiveCD, but not from there and it is quite old. > So what to do with that friendly hint? > > > -- > Bitte senden Sie mir keine Word-, HTML- oder PowerPoint-Anhänge. > Siehe http://www.gnu.org/philosophy/no-word-attachments.de.html > > > ------------------------------ > > Message: 22 > Date: Mon, 09 Jan 2006 19:45:38 -0500 > From: Chris Staub <[EMAIL PROTECTED]> > Subject: Re: Building glibc in section 5.6 > To: [EMAIL PROTECTED], LFS Support List > <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=iso-8859-1; format=flowed > > Clemens HAUPT wrote: > > Am Monday 09 January 2006 23:43 schrieben Sie: > >> This would work. You could also download the LFS live cd. > >> http://www.linuxfromscratch.org/livecd/ > > > > I did it. But what for? For making a bootable CD I need a host > > using Kernel 2.6 at least. With a machine with older Kernel the > > liveCD and all the packages is not of any use. > > I am not sure you understand the idea of the livecd. All you need is to > download the iso image, and have the ability to burn it onto a CD. The > current kernel version is irrelevent as long as you can burn CDs. The > point is that the livecd provides everything you need to build LFS, > including the kernel. > > ------------------------------ > > Message: 23 > Date: Mon, 09 Jan 2006 20:37:02 -0500 > From: Jeremy Huntwork <[EMAIL PROTECTED]> > Subject: Re: Building glibc in section 5.6 > To: [EMAIL PROTECTED], LFS Support List > <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > Clemens HAUPT wrote: > > Absolutly right. BUT! > > You can't do anything with all this nice packages, they are all of > > no use. One might present them to grandma, but neither oneself > > nor grandma can do anything with it when you don't have > > a LINUX Kernel not 2.6 on a single machine. > > The liveCD in that place in not bootable. So if burnt on a CD > > you can decorate your bicycle with it, nothing else. > > I do have a bootable LiveCD, but not from there and it is quite old. > > So what to do with that friendly hint? > > What on earth are you talking about? Of course the CD is bootable. > That's why it's called a LiveCD. > > -- > JH > > ------------------------------ > > Message: 24 > Date: Tue, 10 Jan 2006 12:24:11 +1000 > From: tcp <[EMAIL PROTECTED]> > Subject: gcc error > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Trying to install from the livecd v. 6.1.1.3 stable version and also the > 6.2 pre2 version using the ALFS script but I cannot seem to be able to > get pass the binutils compiling. If I am able to get pass the binutils I > get the same error when it tries to compile the glibc-2.3.4. > > The hard drive I am using is completely blank, I run cfdisk and create 2 > partitions (swap hda1) and (/ hda2). > Run mkswap /dev/hda2 , mke2fs /dev/hda2 .Then I configure the > general.ent and all files required in the skeleton directory then run > runit.sh. > > error: > > -: checking whether the C compiler (gcc ) works... no > -: configure: error: installation or configuration problem: C > compiler cannot create executables. > I: Log file stroed in: > I: /root/.nAFLS/packages/binutils-pass1-2.15.94.0.2.2 > E: Execution failed (1) . > > log file: > > > <?xml version="1.0"?> > <package_log> > <single_try> > <name>binutils-pass1</name> > <version>2.15.94.0.2.2</version> > <package mode="start">Tue, 10 Jan 2006 01:48:47 +0000</package> > <stage mode="start">Tue, 10 Jan 2006 01:48:47 +0000</stage> > <handler_action>Unpacking > /tools/packages-6.1.1/binutils-2.15.94.0.2.2.tar.bz2...</handler_action> > <handler_action>Done unpacking > /tools/packages-6.1.1/binutils-2.15.94.0.2.2.tar.bz2.</handler_action> > <handler_action>Creating directory in /tools/build (parents): > binutils-build</handler_action> > <stage mode="end" status="done">Tue, 10 Jan 2006 01:49:11 +0000</stage> > <stage mode="start">Tue, 10 Jan 2006 01:49:11 +0000</stage> > <handler_action>Patching in > /tools/build/binutils-2.15.94.0.2.2</handler_action> > <handler_action> patch -N -p1 -i > /tools/packages-6.1.1/binutils-2.15.94.0.2.2-gcc4-1.patch</handler_action> > <stage mode="end" status="done">Tue, 10 Jan 2006 01:49:13 +0000</stage> > <stage mode="start">Tue, 10 Jan 2006 01:49:13 +0000</stage> > <stage mode="end" status="failed">Tue, 10 Jan 2006 01:49:17 +0000</stage> > <package mode="end" status="failed">Tue, 10 Jan 2006 01:49:17 > +0000</package> > </single_try></package_log> > > Any help would greatly appreciated > > ------------------------------ > > Message: 25 > Date: Mon, 09 Jan 2006 21:29:48 -0500 > From: Jeremy Huntwork <[EMAIL PROTECTED]> > Subject: Re: gcc error > To: LFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > tcp wrote: > > Trying to install from the livecd v. 6.1.1.3 stable version and also the > > 6.2 pre2 version using the ALFS script but I cannot seem to be able to > > get pass the binutils compiling. If I am able to get pass the binutils I > > get the same error when it tries to compile the glibc-2.3.4. > > > > The hard drive I am using is completely blank, I run cfdisk and create 2 > > partitions (swap hda1) and (/ hda2). > > Run mkswap /dev/hda2 , mke2fs /dev/hda2 .Then I configure the > > general.ent and all files required in the skeleton directory then run > > runit.sh. > > I hope you meant 'mkswap /dev/hda1, mke2fs /dev/hda2'. Also are you > mounting hda2 anywhere? If you try to build LFS on the root filesystem > of the CD without actually mounting the partitions, you're essentially > doing all your work in RAM. > > -- > JH > > ------------------------------ Thanks for the reply JH
Yeah sorry that was a typo I meant mkswap /dev/hda1, mke2fs /dev/hda2, I also did mount the partitions, I found I had bad media that was causing the issue. I had burnt it onto a cdrw, I check the iso and the media with md5sum and the returned the right value, so I thought try different media, so I made a new copy on a cd-r and now no errors during install. I have a new problem now, I managed to stuff grub up and it booted to a blank screen. I have managed to reinstall grub to the MBR and the menu screen appears but when I hit enter to load, it comes up with this error: root (hd0) Filesystem type unknown, using whole disk kernel /boot/lfskernel-2.6.11.12 root=/dev/hda2 Error 17: Cannot mount selected partition Not sure what I have done, or not done... -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
