If you don't know what I mean by build-gcc, read this first: Automated scripts for building gcc 4.4.x and 4.5.x for using with OpenFOAM 1.7 series


Sometime ago, a problem was detected when using one of my build-gcc scripts (see OpenFoam 1.7.0 on RHEL 4.6 post #3) about no valid libc.so being found during the build procedure. This was later fixed by adding the proper lib folder path to LD_LIBRARY_PATH (read post #9 on that thread).

Nonetheless, I rolled up my sleeves and got my hands dirty in trying to build glibc in a simple integrated form in the existing build scripts. But to no avail Attached is my last attempt which almost works, but still fails

I found a hint on how to fix things, but I've got bigger fish to fry *cough*

I also found out that building a more recent version of glibc than the one installed in one's Linux box can be hazardous to the system's health, since problems will start rising from "old" applications trying to use the "new" glibc, leading to system instability and so on.
So, even if I got this to work, it could be all in vain, without providing some additional way to build a whole set of tools for a minimal system to work within the old system (you know, shell tools, building tools, text editors, etc etc). Something similar to MSys for Windows or enough for using a jail root with chroot in Linux/POSIX systems. This is too much of a crazy thing for one man to do on his own, specially when there are better things to in life... or at the very least, crazier things to do in life

SO, if you are nearly or more insane than me, feel free to continue my work and post a comment here if you got somewhere farther than me

If you're afraid about license: it's as OpenFOAM's license - GPL power all the way

Attached Files

build-gcc44experimental.tar.gz (3.9 KB, 240 views)