I rm'ed all of the source port-compile, but largely I did it for space constraints. There were a few I tried to re-cycle and just ended up having to re-un-bzip and recompile anyway becuase I couldn't get a proper compile the second time around. It was a matter of cached config files and the fact that when the programs were linked to the mother hen machine, I didn't have ncurses and a number of other things. The only one I recycled offhand was the kernel source.

Hope that helps,

Cheers,

Finegan

If we keep at this, we might over-take The anti-microsoft thread...

Nah...

Finny.

Good job...All is well it sounds. Yeah, remove all of the original source. It's recommended in the book because you can get a lot of goofups working off old source. So I just rm -rf the directories and when you get to the point of chrooting in, you'll just re-bunzip them all and do it again anyhow. Best to work off fresh source.

Oh yeah, but keep the kernel source, that's fine. Leave $LFS/usr/src/linux

okie dokie... gonna start my LFS this week, so if I have any questions gonna be posting here, if not.. I might get lost in my little world of making my own LFS system based off Slack!! Woo hoo.. can't wait.

It is a blast and my hints for what they're worth are these: The most important is to d/l the lfs-bootscripts and lfs-commands files. The bootscripts you just copy over instead of writing out a but*load of script. As you go through the book, open another console and use lfs-commands and follow by chapter. If you can cut 'n paste, you'll have it done in half the time. I spent today completely redoing my LFS and instead of three days it was 8 hours. the name changed too... =} But that's me, if you wanna type it all out, that's always the best way to learn, but i did that the first time...not again.

cool, yeah.. i was going to download the boot scripts.. look at them but i might actually type them all out.. doing everything slowly to get a deep inside look at everything.. or at least read thru all of them..

yeah, most likely i am going to get it working the long way first.. then going to redo it again in a quicker manner to set everything in place.

not sure what i am gonna name mine yet.. tricky linux... hmmmmm... kiddy linux.. i come up with something probably by the time i am done.

Hi again

I was just wondering if I need to set up compiler optimizations like the book states, for everything except glibc ofcourse because that can cause problems apparently, and if so how would I go about it?

My base system is Mandrake which is i586 anyway do I need to, what did you guys do?

Thx guys

RecoilUK

Need to? Not really. You can optimize your compiler so it compiles binaries that will only run on one architecture series and everything above that. For instance, if you download a new kernel these days, its set to compile optimized for a PIII, and won't even run on a PI. Bummer, as that's half my house. Mandrake compiles the whole distro optimized for i586, the PI, just because they want to eek out some performance over their bloat... er, sorry, did that sound cruel? Regardless, its not necessary, but if you want you can optimize for i586, i686, whatever your machine is, and you will get some speed out of it. Then again, I've stuck proftpd, ssh, telnet, netdate, traceroute, nmap, fingerd, and a half a dozen other things on my default compiled i386 LFS and haven't noticed it slow down from maniac fast yet.

Cheers,

Finegan

I wouldnt mind doing it, but I have no idea how to, any tips? and should I have been doing it allready, i,m just starting chapter 6?

L8rs

RecoilUK

Hi again

I dont think i,ll bother with the optimizations after all.

When installing the programs in chapter 6 are you supposed to do it in the order from the book, or can you do it in any order? the reason i,m asking this is because I,m having problems with the first package..as follows..


../glibc-2.2.4/configure --prefix=/usr \
--enable-add-ons --libexecdir=/usr/bin

creating cache ./config.cache
checking host system type... ../glibc-2.2.4/scripts/config.guess: cat: command not found
i586-pc-linux-gnu
../glibc-2.2.4/configure: cat: command not found
checking sysdep dirs... sysdeps/i386/elf linuxthreads/sysdeps/unix/sysv/linux/i386 linuxthreads/sysdeps/unix/sysv/linux linuxthreads/sysdeps/pthread sysdeps/pthread linuxthreads/sysdeps/unix/sysv linuxthreads/sysdeps/unix linuxthreads/sysdeps/i386/i586 linuxthreads/sysdeps/i386 sysdeps/unix/sysv/linux/i386 sysdeps/unix/sysv/linux sysdeps/gnu sysdeps/unix/common sysdeps/unix/mman sysdeps/unix/inet sysdeps/unix/sysv/i386 sysdeps/unix/sysv sysdeps/unix/i386 sysdeps/unix sysdeps/posix sysdeps/i386/i586 sysdeps/i386/i486 sysdeps/i386/fpu sysdeps/i386 sysdeps/wordsize-32 sysdeps/ieee754/ldbl-96 sysdeps/ieee754/dbl-64 sysdeps/ieee754/flt-32 sysdeps/ieee754 sysdeps/generic/elf sysdeps/generic
checking for a BSD compatible install... /bin/install -c
checking whether ln -s works... yes
checking for pwd... /bin/pwd
checking build system type... i586-pc-linux-gnu
checking for gcc... gcc
checking version of gcc... 2.95.3, ok
checking for gnumake... no
checking for gmake... no
checking for make... make
checking version of make... 3.79.1, ok
checking for gnumsgfmt... no
checking for gmsgfmt... no
checking for msgfmt... no
checking for makeinfo... makeinfo
checking version of makeinfo... 4.0, ok
checking for gsed... no
checking for sed... sed
checking version of sed... 3.02, ok
checking whether the C compiler (gcc ) works... ../glibc-2.2.4/configure: cat: command not found
../glibc-2.2.4/configure: cat: command not found
no
checking whether the C compiler (gcc ) is a cross-compiler... (cached) yes
checking whether we are using GNU C... ../glibc-2.2.4/configure: cat: command not found
no
configure: error: GNU libc must be compiled using GNU CC

I have followed the instructions to the letter, but i,m still getting the above errors? does anyone have a possible cause and solution this?

Thx guys

RecoilUK

It looks like from the error that you're missing cat, which should have been installed with the last of the goop from Textutils2.0 in the very last bit of Chap 5,
here. Try cat'ing any file just to see if you have it and that its working. If not, re-bunzip, re-compile, and re-install textutils. Then, when you go back to re-do glibc, make sure you've run a make clean before you start.

Cheers,

Finegan

P.S. perfect idea posting your config output.

Thx for the answer FINEGAN thats what it was.

Oh and I normally wouldnt post it, but it was short enough this time to warrant it

Thx again

RecoilUK

Yeah, install them in that order or you might (probably) will start getting more errors. Such as a compile needing something else installed first.

My Go* have you seen all that crap you have to type? I must say that's admirable. I would go crazy. But you're right, the in depth will tell you alot more than just copying the scripts. I typed everything else the first time though and that's not too bad. I went and redid mine like I said and just cut n' pasted. I only have one error on boot. I'm pretty pleased with that and it's an easy one. I hope.. LOL It's quite the fast little Fu****!