Re: Precompiled Temporary Toolchains
On Tuesday 12 September 2006 04:47, [EMAIL PROTECTED] wrote: does anyone have a precompiled temporary toolchain so that i don't have to recompile over and over again? The following is my own opinion. 1. Anything precompiled breaks the whole idea behind Linux From Scratch. 2. Toolchain compiled on another host may even be not runnable because of dependencies on toolchain builder's host system. Anyway these dependencies should be avoided. In other words, you cannot just take somebody else's temporary toolchain and use it. You should at least make sure it's compiled in an environment similar to your one. I prefer to spend some time in recompiling over and over again rather then be constantly afraid of the toolchain being incompatible with my environment (especially host glibc, gcc, binutils, kernel-headers). I think that's why the book says to use temporary toolchain for building the resulting system rather than to use the host system for this purpose. -- Nothing but perfection pv -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Precompiled Temporary Toolchains
On 9/12/06, Vladimir A. Pavlov [EMAIL PROTECTED] wrote: On Tuesday 12 September 2006 04:47, [EMAIL PROTECTED] wrote: does anyone have a precompiled temporary toolchain so that i don't have to recompile over and over again? In other words, you cannot just take somebody else's temporary toolchain and use it. You should at least make sure it's compiled in an environment similar to your one. Good advice. Here's another thought. If you keep recompiling over and over, why don't you just tar up /tools? Then you have a precompiled temporary toolchain. Just do the tarring before the the Ch. 6 toolchain adjustment. The advice at the end of Ch. 6 is bogus. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: coreutils-5.96
On Sunday 10 September 2006 09:59, Wei Chong wrote: src/su dummy -c make RUN_EXPENSIVE_TESTS=yes check the test fail with following error: Making check in lib /bin/sh: line 0: cd: lib: Not a directory make: *** [check-recursive] Error 1 Does lib folder exist in coreutils-5.96 build directory? Run the following having replaced the folder path with your one. ls -ld /build/coreutils-5.96/lib -- Nothing but perfection pv -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: No sound from speakers
On Tue 12 Sep 2006 Dan Nicholson wrote: The alsa.dev script was used when hotplug and udev were installed together. Hotplug handled dynamic devices, and it would use the alsa script placed in /etc/dev.d. Nowadays, udev has completely deprecated hotplug to the point where any of the dynamic actions are defined in udev rules. But, that happened in between LFS-6.1.1 and LFS-6.2. So, what version of LFS are you building on? I'm sorry I should have said. I'm building on LFS-6.1.1 which is why I'm using the BLFS-6.1 book. Richard -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Package users: wrapper script for mkdir
On Sat, 9 Sep 2006 15:24:48 +0300 Angel Tsankov [EMAIL PROTECTED] wrote: I checked that the version I am using is 5.2.1 from the coreutils package: I see. Well I tried it with shadow's su because that's what we use on the finished LFS system. Could well be that coreutils' su doesn't work properly in this respect. You could try building shadow's su in chapter 5. MSB -- Socialism might have worked, had it been more social and less ism. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: error installing texinfo-4.8
On Tuesday 12 September 2006 03:32, mike wrote: Hi there, i don't know if anyone can offer any help but i'm when i try in install texinfo-4.8 i'm getting undefined reference to 'tgetstr' undefined reference to 'tgetflag' error messages before make fails What version of LFS book do you use? What is the chapter where the error appears? Can you please show the last 20-30 lines of failed make's output? This information would help to solve your problem (or to reproduce it at least). -- Nothing but perfection pv -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Package users: wrapper script for mkdir
I checked that the version I am using is 5.2.1 from the coreutils package: I see. Well I tried it with shadow's su because that's what we use on the finished LFS system. Could well be that coreutils' su doesn't work properly in this respect. You could try building shadow's su in chapter 5. Well, I found out how to make it work as I need it to: su -- user_name -l -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Precompiled Temporary Toolchains
Dan Nicholson wrote: The advice at the end of Ch. 6 is bogus. -- Dan -- Would you care to elaborate? Thx -Brandon -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Precompiled Temporary Toolchains
On 9/12/06, Brandon Peirce [EMAIL PROTECTED] wrote: Dan Nicholson wrote: The advice at the end of Ch. 6 is bogus. Would you care to elaborate? Thx A long standing hammering of /tools done in the toolchain readjustment. When you finish Ch. 5, /tools is well fleshed out and the toolchain is properly set to compile programs that link into /tools/lib, etc. Then you get to the Ch. 6 readjustment and you change the default ld (in /tools) and add a specs file (in /tools) so that compiled programs will link to /lib, etc. in the chroot. This achieves the proper effect as you don't want your final gcc and binutils linking against the temporary system. However, when you get to the end of Ch. 6, it says you can tar up /tools and use it again. Wrong. Now your toolchain in /tools points to /lib and friends. If you move the old ld back in /tools/bin and remove the specs file, all is well. Then you really can unpack /tools and start firing away in Ch. 6 on a blank disk. The way it is now, a tarred up /tools provides nice temporary tools if something is messed up, but it doesn't give you a clean starting point if you were trying to build a pure final system. The changes in /tools to adjust the toolchain are not really necessary. There are other methods where the changes could be made without affecting anything in /tools (beware of flame wars, though :). See how DIY does the readjustment and subsequent gcc and binutils builds: http://www.diy-linux.org/x86-reference-build/chroot.html#c-readjust-toolchain -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
