[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

building glibc not with the default system compiler

From: Dino Klein
Subject: building glibc not with the default system compiler
Date: Fri, 20 Sep 2002 08:46:01 -0400

This is a problem I had back in August, when I could still compile glibc
from CVS. Ever since, trying to build from CVS doesn't work for me anymore.
I decided to post this, in case it might be an issue.
Description follows:

I've ran into this issue some time ago (around August), when I tried to
compile glibc with gcc-3.2.
I have gcc-3.2 installed under my home directory, so programs requiring its
libgcc.so need to have LD_LIBRARY_PATH set.
The problem I have is during "make check"; when the tests which use c++ code
are run, they cannot resolve libgcc.so, since it is not in one of the paths
provided explicitly to ld.so.
What I've done, in order to try and get around this is to export CC, CXX,
CPP, LD_RUN_PATH, and LD_LIBRARY_PATH, so they point to my gcc32
installation, and are available during the configure, make and "make check"
It seems like the build scripts assume glibc will be build by the default
compiler, and hence its libraries will always be available in /usr/lib.
In order to actually complete the check process, I've modified the
"trusted-dirs.h" file, in the build directory, so it has the ~/gcc32/lib
directory listed in it. This solves the problem, but if I'm not mistaken -
this directory gets imprinted in the ld.so executable, which should be used
only for testing purposes and not on a system where glibc is installed.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]