08-Oct-04 --------- I built glibc with gcc-3.3.4 and whilst glibc compiled and appeared to work, I found that NFS breaks - transferring (cp, tar, whatever) large files (over a few hundred K) causes the process to enter uninterruptable sleep - waiting on i/o. I will probably never compile glibc again without gcc-3.3.2 which is why this evening I have made a new package and build script for gcc-3.3.2. Aggr. 15-Jul-04 --------- When building glibc natively (which ARMedslack's now is), you should compile using gcc 3.3.2 as this is what I have tested it with since I first booted ARMedslack in Feb 04. I keep copies of older gcc versions inside armedslack-current/testing/packages # cd gcc-3.3.2 # upgradepkg gcc*.tgz Then build glibc-2.3.2. If you do get it to compile and have glibc *work* with newer compilers then please let me know. Last time I tried with gcc 3.3.4 it broke and I don't have time to spend trying out different compilers when I know that 3.3.2 works and produces a working glibc. If you have any trouble with autoconf (as I did during my experimentation with glibc-2.3.3) then you may need to : # removepkg autoconf2.13 autoconf # installpkg d/autoconf-*.tgz -------------------------------------------------------------------- Scratchbox build notes ---------------------- Prerequisites for building inside Scratchbox 0.9.7 (0.9.8 is fixed): As root on your x86 Slackware system: ( cd /usr/bin cp -fa rpcgen localedef /scratchbox/alien_tools/bin /scratchbox/tools/bin/alien_tool_links ) Now we're ready to rock and roll. 06-Jun-2004 ------------ Ensure that we: a) do not have an existing glibc installed (sboxsysrestore) b) scratchbox is not using binutils-2.15. I have heard that glibc-2.3.2 does not build with anything other than binutils 2.14 (although it builds for me, it doesn't work!) ** DO NOT USE WITH SCRATCHBOX 0.9.8. YOUR GLIBC WILL BREAK ** After running slackware/tinstall.sh, I chrooted into the new image via one of my existing ARMedSlack boxes. bash started correctly but as soon as I ran an non-built in (ie 'ls'), ls displayed the dir list, exited but never returned to a bash prompt. This was replicated by attempting to boot the system on one of the other ARMedSlack development machines. I thought that it may have been because I changed Debian diff release from 11 (tried and tested by myself for 5 months) to lucky number 13. However, I ruled out this possibility by re-building with diff 11. I have not worked out the cause of the problem. It may be: [1] be a compiler issue. I have heard that glibc doesn't work properly for some archs (alpha, I think) with gcc 3.3.3 but does with gcc 3.3.2 (which Scratchbox 0.9.7 uses). [2] because I've used qemu in sb0.98 rather than sbrshd in 0.97 There are a few failures (unsupported system call) when creating locale data under qemu, but I'm not convinced that would be the problem. However, there could be other errors that I have missed. I want to build glibc natively, but for the moment I'll stick to building it inside sbox 0.9.7 and gcc 3.3.2, as it's been stable since Feb 2004 when I first built it. -- Stuart Winter