Error building Glibc-2.14

an1L · 03-23-2012, 07:06 AM

Hi,
I'm trying to install glibc to debug a C-framework I'm working on. But, I'm getting an error in the build process. Here's the error msg:

Code:

make[3]: Leaving directory `/root/glibc-source/glibc-2.14/elf'
/usr/bin/install -c /root/glibc-2.14-build/elf/ld.so /usr/local/myglibc/lib/ld-2.14.so.new
mv -f /usr/local/myglibc/lib/ld-2.14.so.new /usr/local/myglibc/lib/ld-2.14.so
/usr/bin/install -c /root/glibc-2.14-build/libc.so /usr/local/myglibc/lib/libc-2.14.so.new
mv -f /usr/local/myglibc/lib/libc-2.14.so.new /usr/local/myglibc/lib/libc-2.14.so
echo ld-2.14.so /usr/local/myglibc/lib/ld-linux-x86-64.so.2 >> /root/glibc-2.14-build/elf/symlink.list
/usr/bin/install -c /root/glibc-2.14-build/elf/sotruss-lib.so /usr/local/myglibc/lib/audit/sotruss-lib.so.new
mv -f /usr/local/myglibc/lib/audit/sotruss-lib.so.new /usr/local/myglibc/lib/audit/sotruss-lib.so
make[2]: *** No rule to make target `/root/glibc-2.14-build/dlfcn/libdl.so.2', needed by `/root/glibc-2.14-build/elf/sprof'.  Stop.
make[2]: Leaving directory `/root/glibc-source/glibc-2.14/elf'
make[1]: *** [elf/subdir_install] Error 2
make[1]: Leaving directory `/root/glibc-source/glibc-2.14'
make: *** [install] Error 2

Any suggestions?

Thanks

John VV · 03-23-2012, 03:41 PM

you really do NOT want to build glibc
that IS the operating system

now if this OS is " Linux from scratch "
then read the book

but if you try to change out the already installed version you will destroy your install

now it is "possible" to install a second version for a custom built program --- but it is not that easy

if you are trying to have "debug" installed then install the debug packages from your package manager

glib 2.14 ? i am guessing this is fedora 16

do a yum search for the debug rpm

an1L · 03-24-2012, 11:51 AM

Thanks for your reply John.

I'm aware of the potential problems with meddling with libc. That's why I'm trying to install it separately independent of the system library.

I had built glibc on the same machine earlier last week without any errors. I'm rebuilding it because glibc is compiled with optimization level 2(-O2) by default and I'm unable to look into the values of a few variables inside the library functions from the code dump as they've been optimized out. I'm now trying to build it with optimization level 1 but haven't been able to succeed so far.

I'm using RHEL 6.2.

John VV · 03-24-2012, 10:44 PM

it has been a bit .I normally would need to build glib and a few other things for the development version of gimp ( i have not done that for a while )

Quote:

I'm using RHEL 6.2

the first thing is you will want to check with red hat and make 100% sure that installing a second glibc will not kill the support contract
It should not on a home system but if this is in the office ???????

now depending on just what software needs this very NEW version
fedora 16 or 17 might be a better OS to use fedora is currently using that version

cent/ RHEL 6.2 is using - 32 bit
glibc-2.12-1.47.el6.i686.rpm

first the os CAN NOT SEE the new version .It can NOT be in the system path
also you might also need to build packageconf and autotools for the new glibc

in the configure line along with all your customizations use "-prefix=/opt/glibc2.14 "
( for gimp-development i would but it in
/usr/opt/Gimp-TESTING/glib2.?????? )

then export that location for the software that REQUIRES this new version , when you build it
if it is NOT a make file project then you will also need to export the new glibc packageconf folder
/opt/glibc2.14/lib/packageconf/glib.????.pc

from the error in the first post it dose not look like configure finished
at least one make file was not made

you might want to read the configure.log to see just where it stopped
and have a look at
"linux from scratch " chap 5
http://www.linuxfromscratch.org/lfs/...r05/glibc.html

PS.
to add
this new version might need a ALL new build and support tree
so you might end up building 90% of fedora 16
just to get this new version running on RHEL 6.2

so a warning take care you might be only building 100 meg of source
or you might end up building 4 Gig of source code

an1L · 03-26-2012, 05:06 AM

Quote:

the first thing is you will want to check with red hat and make 100% sure that installing a second glibc will not kill the support contract

I'm working on a development system which is bound to crash frequently and hence is not supported, so no worries there

.

I re-installed the library again but this time I did make all before I did make install. Not sure how this made a difference but its working fine now. I can now step into the rpc library function where my program was crashing due to a segfault. However, I still can't print the value of some of the variables from gdb as they've been optimized out. I'll try rebuilding glibc with a lower optimization level again.

Any idea on how I can turn off this particular feature of gcc while compiling the library?

Thanks