Re: Glibc Testing Errors

2010-10-24 Thread John Mitchell
Hi, This is my first crack at LFS. I'm wandering if the error associated with the link below was ever resolved? *Previous and related errors:* http://www.mail-archive.com/lfs-support@linuxfromscratch.org/msg14143.html *My setup:* - Book 6.7 - 64 bit -- athlon x2 - host kernel =

Re: Glibc Testing Errors

2010-10-24 Thread John Mitchell
FYI: The compiler segfault below created one of my test errors that I reported earlier. -- This is one I guess I can legitimately ignore? Not sure about the remaining errors: make[2]: [/sources/glibc-build/posix/annexc.out] Error 1 (ignored) make[2]: ***

Re: glibc (stage 2) make install error

2010-10-24 Thread John Mitchell
Casey, Hmm... it appears that you didn't run one of the commands given in the book. QUOTING FROM THE BOOK: Section 6.9 When running *make install*, a script called test-installation.pl performs a small sanity test on our newly installed Glibc. However, because our toolchain still points to the

The system has no more ptys. Problem.

2010-10-24 Thread sannikov
Hi. I build lfs 6.7 and on step 6.12. Binutils-2.20.1 have next problem: root:/sources/binutils-build# expect -c spawn ls spawn ls The system has no more ptys. Ask your system administrator to create more. while executing spawn ls Seems that all steps before - is Ok. All founded solves

Re: The system has no more ptys. Problem.

2010-10-24 Thread Andrew Benton
On Sun, 24 Oct 2010 21:42:27 +0400 sannikov sanni...@cs.karelia.ru wrote: Hi. I build lfs 6.7 and on step 6.12. Binutils-2.20.1 have next problem: root:/sources/binutils-build# expect -c spawn ls spawn ls The system has no more ptys. Ask your system administrator to create more.

Re: The system has no more ptys. Problem.

2010-10-24 Thread sannikov
On Sun, 24 Oct 2010 19:07:35 +0100, Andrew Benton b3n...@gmail.com wrote: On Sun, 24 Oct 2010 21:42:27 +0400 sannikov sanni...@cs.karelia.ru wrote: Hi. I build lfs 6.7 and on step 6.12. Binutils-2.20.1 have next problem: root:/sources/binutils-build# expect -c spawn ls spawn ls The

LFS-GMP-5.0.1

2010-10-24 Thread Dr.-Ing. Edgar Alwers
Hi Bruce, I have finisched building LFS-6.6. It is working smootly, it tooks only a few days to build it. Thank you very much for all the work involved with the book ! It is an excellent guide. I used Fedora 13 as a basis this time. Talking about LFS SVN-20101018. The compilation of GCC-4.5.1

Re: LFS-GMP-5.0.1

2010-10-24 Thread John Mitchell
Hi Edgar, I'm curious about your Fedora 13 basis. I have been using RH and Fedora for many years but never really dug into linux like this. I have finally become frustrated enough with the maintenance/upgrade issues that I decided to take more control. Can you perhaps describe (to whatever

Re: Version 6.7: Chapter 6.9.3. Configuring the Dynamic Loader

2010-10-24 Thread Bruce Dubbs
John Mitchell wrote: Hi, I'm wandering if it makes any sense to configure /etc/ld.so.conf to include lib64 directories - /usr/local/lib64 - /opt/lib64 I guess this can always be added later? Yes. Note that LFS does not build a multilib system as multilib is not needed if

6.10. Re-adjusting the Toolchain

2010-10-24 Thread John Mitchell
Hi, I don't quite understand how re-writing the 'specs' file under the '/tools' directory actually works -- by the way it does work!. The specs file that is written with the fancy 'sed' script shows up as: /tools/lib/gcc/x86_64-unknown-linux-gnu/4.5.1/specs I don't get how writing the spec

Re: Book-5.8_Adjusting the ToolChain (v6.7)

2010-10-24 Thread lfs
On 10/23/10 04:04, Andrew Benton wrote: /tools is available in chroot, that's why we make the /tools = /mnt/lfs/tools symlink. The programs are installed into /tools, the linker links to it's libraries in /tools/lib. Then when you're in chroot everything is in the right place using the

Re: Book-5.8_Adjusting the ToolChain (v6.7)

2010-10-24 Thread Bruce Dubbs
lfs wrote: On 10/23/10 04:04, Andrew Benton wrote: /tools is available in chroot, that's why we make the /tools = /mnt/lfs/tools symlink. The programs are installed into /tools, the linker links to it's libraries in /tools/lib. Then when you're in chroot everything is in the right place