You are not logged in.
I've been doing a search on glibc 2.4 & gcc 4.1 at the forums, and before anyone jumps the gun, I'm not wondering why they're not in the offical repos.
However, I'd like to do some playing around for myself so I've been trying to write pkgbuilds for glibc 2.4 (to start with). My pkgbuilds, based on the offical glibc, haven't really worked for me, so if anyone else is playing around with glibc 2.4 and has a working pkgbuild, I'd love to take a look at it.
Cheers.
Offline
Wait a second, be patient.
There is gcc-4.2.0 release almost on the load.
I am doing glibc/gcc/binutils stuff myself.
To upgrade glibc stuff, i always using RIP
IMHO, upgrading gcc aren't harmful but glibc, should be careful.
> cc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc/configure --prefix=/usr --libexecdir=/usr/lib --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-languages=c,c++,java,treelang
Thread model: posix
gcc version 4.2.0 20060506 (experimental)
>I removed my sig, cause i select the flag, the flag often the target of enemy.
SAR brain-tumor
[img]http://img91.imageshack.us/img91/460/cellphonethumb0ff.jpg[/img]
Offline
Thanks, I've never heard of RIP before. I'll take a look into it.
I'm mostly doing this for learning purposes, and it's being done on a separate installtion of Arch, so it doesn't matter if I bork stuff seriously ![]()
Offline
RIP is only needed to change symlinks /lib/tls/* or /lib/* of glibc shared libraries.(chroot)
After or before upgrade, you have to compile almost system-utils/apps with newer glibc..
IMHO, it will be good if glibc concurrent ability like erlang style.
more information is here
http://bc.tech.coop/blog/060509.html
I removed my sig, cause i select the flag, the flag often the target of enemy.
SAR brain-tumor
[img]http://img91.imageshack.us/img91/460/cellphonethumb0ff.jpg[/img]
Offline
glibc 2.4 will drop compatibility with kernel 2.4, so we want to upgrade to that after the 0.7.2 release. GCC 4.1 will cause breakage on many programs, for example KDE, we can't compile kdelibs with 4.0 and compile kdebase with 4.1 without getting weird issues. If we update one, we have to update them all, which means we have to patch up many things to get them working with gcc 4.1.
After we release 0.7.2 officially, we'll switch to gcc 4.1 and glibc 2.4 and probably some newer version of binutils.
Offline
linux kernel and NVidia-installer(NVIDIA-Linux-x86-1.0-8756-pkg1.run) and garnome(2.14.1) works fine with gcc-4.2 snapshot version on my arch, here.
> uname -a
Linux arch 2.6.17-rc3-git18 #1 PREEMPT Thu May 11 23:28:17 XXX 2006 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz GenuineIntel GNU/Linux
>glibc-2.4(not yet? i have no time), binutils-2.17(not yet? i have no time), gcc-4.2 all fine with my arch.
I removed my sig, cause i select the flag, the flag often the target of enemy.
SAR brain-tumor
[img]http://img91.imageshack.us/img91/460/cellphonethumb0ff.jpg[/img]
Offline