My OS News
So its been a while, but I have some updates on my OS escapades.
First, I bought a new computer (well, my wife bought it for me), its an HP a6750y, Quad-Core AMD CPU, 8g of RAM, an onboard ATI HD3200 video card (which I replaced with an old ATI X1300 Pro from my old computer), and a 750g hard-drive. It came pre-installed with Vista 64-bit Home Edition, which isnt exactly my cup of tea, but honestly I just dont have the energy to try and roll it back to XP.
Anyways, I installed Kubuntu 8.10 as a dual-boot, along with the new Windows 7 Beta. I’m loving Kubuntu, and if I can find a way to get WoW and a few other games working I’m saying goodbye to Windows. However, there has been a slight hitch. I can’t seem to get the ATI/AMD proprietary drivers to activate through the Hardware Drivers program. For some reason it just greys out the listing for the driver and does nothing else. Oh well, the fight continues. Once I get the graphics working I’ll try to get the games up and running.
Until then, I’m having fun with Kubuntu.
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. Googling ‘glibc 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.
