hi folks,

compiled and packaged glibc into an rpm....CHECK
installed it into a test directory ...CHECK
chroot into the test directory....FAILED!

the reason is because glibc seems to be looking for ld.so.cache or ld.so.conf in the wrong directories (namely the BUILDROOT directory of the rpm system which is of course different from the test chroot directory)

the question is , how can i stop glibc from hardwiring the default location for those cache and config files or at least change those locations post-compilation ?

when running ldconfig of the newly installed glibc , the error is made clear but i don't know how to correct it...help is needed

cheers

Please have a look into a glibc.spec from a glibc.SRC.RPM.

Example Fedora 15 glibc-2.13.90-9.src.rpm
http://download.fedora.redhat.com/pu...3.90-9.src.rpm


$ grep -n ld.so.cache glibc.spec :

533:> $RPM_BUILD_ROOT/etc/ld.so.cache
987:%attr(0644,root,root) %verify(not md5 size mtime) %ghost %config(missingok,noreplace) /etc/ld.so.cache

etc. etc. : 1050 lines spec file to build glibc.

..

0 members found this post helpful.

Okay ...and how exactly is that supposed to solve my problem?
the fact that fedora's glibc specs file is 10 times bigger and more complicated than mine (with less than 50 lines) , is just one reason why i don't find it useful to peek at other people's work , second reason is that my distro is nothing like Fedora and the third being that you're missing the Woods for the Trees.

to recap , i've a very specific problem which is that , during configuration autoconf script is told via the rpm specs file and the config parameter file to install the files into specific locations for later packaging by rpm (which is obviously BUILDROOT)

E.X
and with configparam in BUILD directory containing something like:
THE PROBLEM , is that during compilation the libc object libraries are apparently given the above path (i.e $RPM_BUILD_ROOT/etc ) to be hardwired into them , meaning that once glibc is packaged and installed/relocated into its final directory it will no longer find ld.so.conf or ld.so.cache .

NOTE: needless to say this problem would not arise if RPM wasn't involved.

so the Question is : How can i tell the Autoconf script to NOT hardwire the above given path into them when looking for the conf/cache files or at least to hardwire something else (i.e the correct path) ??

cheers

Well i've found the solution myself.

and that is to use the 'install_root' argument with 'make install' such as in:
while setting all other arguments in configparam or in the configure as if the installation will go into / by default !

this will relocate glibc into the chroot or test directory without messing up the hardwired scripts paths .

cheers

1 members found this post helpful.