This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/10063] 'configure' for glibc-2.9 does not check libgcc_s.so.1 presence, test fail
- From: "sergstesh at yahoo dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 13 Apr 2009 23:17:33 -0000
- Subject: [Bug libc/10063] 'configure' for glibc-2.9 does not check libgcc_s.so.1 presence, test fail
- References: <20090411230411.10063.sergstesh@yahoo.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From sergstesh at yahoo dot com 2009-04-13 23:17 -------
(In reply to comment #6)
> Sergstesh, I think Ulrich's point is that everyone who normally needs to build
> glibc (hackers and packagers) figured out how to do it and while making this
> process easier for newcomers might be nice, it's nowhere near being a priority
> for any glibc developer - potential new developers need to strap in for much
> more anyway and expanding the user base is irrelevant in this case. So if you
> want to have this fixed, you need to do all the work up to a final patch
> yourself and noone will probably even be much willing to spend time supporting
> you in the process.
(In reply to comment #6)
Too many words have been spent for nothing - I mean both bug reports of mine.
So, I have a practical question to which I can fins an answer myself, or to
which I can get the answer is shorter than the all the words already said in
vain, and the question is:
what mechanism WRT file paths is used to load, where necessary, libgcc_s.so.1:
1) absolute path related to system locations, like /lib, /usr/lib, etc.;
2) no path at all, but rather contents of LD_LIBRARY_PATH or another environment
variable ?
3) a path calculated according to 'gcc' directory tree, e.g. 'gcc' is
/mnt/sdb8/sergei/AFSWD_debug/install/gcc-4.3.3/bin/gcc
, so its bin directory is simply
dirname(/mnt/sdb8/sergei/AFSWD_debug/install/gcc-4.3.3/bin/gcc) , i.e.
/mnt/sdb8/sergei/AFSWD_debug/install/gcc-4.3.3/bin
and, consequently, the 'lib directory is
/mnt/sdb8/sergei/AFSWD_debug/install/gcc-4.3.3/bin/../lib ==
/mnt/sdb8/sergei/AFSWD_debug/install/gcc-4.3.3/lib
?
I can answer the answer myself because I know about LD_DEBUG environment
variable and I have already tried it, though not yet in the places I need to
nail down this issue, but it will take more time from me than from those whi
know the answer "by construction".
Thanks in advance.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10063
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.