INCLUDE_DATA

New New beginnings…

Ok, so the FreeBSD didn’t work out for me, I don’t have any blank CD’s left and dont have the ability to merge all the CD’s into a DVD. Since all I have are multiple blank DVD’s, I’m downloading slackware 12.0 and gonna throw that at my box…hmm, sounds kinky, doesn’t it?

I am currently listening to: Snot - Absent

The dead shall rise…

w00t! I got my 120gb Seagate working again, so I think I’m gonna use my project box as file storage for a while. That is all.

I am currently listening to: MetallicA - Disposable Heros

New Beginnings…

Ok, so after hour of getting nowhere, I decided to scrap the LFS project until I get a better understanding of the whole *nix thing. So I’m installing a pre-made distro, FreeBSD. I chose FreeBSD as opposed to NetBSD and OpenBSD as it seems to be the most ‘universal’ and newbie friendly BSD version.When I find an actual purpose for the project box, I might reconsider to using OpenBSD (which is renowned for its security) and NetBSD (which is known for its server capabilities and ability to run on almost any hardware configuration). Hell, I might even try a few Linux distro’s before any of that. Until then, it’s my little project box AND IT SHALL OBEY MY EVERY COMMAND!

 

…well, we’ll just forget the whole LFS fiasco for now and pretend like it never happened…

I am currently listening to: Live - Lightning Crashes

Progress Report - Chapters 6.10-6.11

Ok, so I had a small problem with ‘Re-adjusting the Toolchain‘ in Chapter 6.10. Seems that in Chapter 5.12. Binutils-2.17 - Pass 2 I forgot the very last
cp -v ld/ld-new /tools/bin
command, and it borked things up in Chapter 6.10. After hours of help from ChrisS67 (current founder of LFS-Support) in the #lfs-support channel on irc.linuxfromscratch.org eventually I had to go back and re-do the binutils pass 2 chapter and everything was fine. Thank a million ChrisS67!

Anyways, after we got that figured out, I was able to finish Chapter 6.10 and Chapter 6.11. Binutils-2.17. I’m calling it a night as I’m exhausted. G’night folks.

glibc-2.5.1 Compiling Issues - Chapter 6.9

Ok, I made it through to Chapter 6.9, where I have to re-compile glibc-2.5.1 for the real system. I use the following steps:

tar -xvf ../glibc-libidn-2.5.1.tar.gz
mv glibc-libidn-2.5.1 libidn
sed -i ‘/vi_VN.TCVN/d’ localedata/SUPPORTED
sed -i ’s|libs -o|libs -L/usr/lib -Wl,\
-dynamic-linker=/lib/ld-linux.so.2 -o|’ scripts/test-installation.pl
sed -i ’s|@BASH@|/bin/bash|’ elf/ldd.bash.in
mkdir -v ../glibc-build
cd ../glibc-build
../glibc-2.5.1/configure –prefix=/usr –disable-profile \
–enable-add-ons –enable-kernel=2.6.0 –libexecdir=/usr/lib/glibc
make
make -k check 2>&1 | tee glibc-check-log
grep Error glibc-check-log

This resulted in:

make[2]: *** [/sources/glibc-build/dlfcn/bug-atexit3.out] Error 1
make[1]: *** [dlfcn/tests] Error 2
make[2]: [/sources/glibc-build/posix/annexc.out] Error 1 (ignored)
make[2]: *** [/sources/glibc-build/nptl/tst-cancel1.out] Error 1
make[2]: *** [/sources/glibc-build/nptl/tst-cancel24.out] Error 127
make[1]: *** [nptl/tests] Error 2
make: *** [check] Error 2

Ouch. The posix/annexc, nptl/tst-cancel1, and nptl/tst-cancel24 errors are expected, as per Chapter 6.9 - glibc of the LFS manual. The only problem is that I cannot seem to find any solutions or explanations of the atexit3 error. Googlingglibc atexit3‘ found very little. This post however suggested the --with-arch=i486 flag on the configure script. Of course, thinking I was smart, I used --with-arch=i686, thinking “Yeah, that’s what ./config.guess from the binutils package told me the architecture is, that must be it.” I was wrong. Still the same error. So now I’m trying with the --with-arch=i486 configure flag, I’ll let you know when it finishes…

It seems that this guy had the same problems, but he hasn’t posted a solution…

Update 2.11.2008 1:49p.m.: Ok, after sleeping, drinking some dew, and giving it another shot, I come back to try grep Error glibc-check-log again, but I get the same results. Then of course, I realize that I didn’t clean out the old build files before trying again, so I removed the glibc-build directory and remade it, went in and re-configured it with the --with-arch=i486 flag. Still same problem as before. I’ve still got some feelers out there to see if I can’t figure out if this is a show-stopper, or if I can ignore it. I’ll keep you updated.

Update 2.11.2008 10:55p.m.: Ok, so after hitting a few mailing lists and more than a few IRC channels, I get the general response of “It’s O.K., ignore it”, so that’s what I did. I’m continuing on with the project as-is.

Next Page →