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: 12 Apr 2009 21:09:25 -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-12 21:09 -------
(In reply to comment #2)
> You have really no idea what you're talking about. libgcc_s is used at runtime
> and LDFLAGS has nothing to do with that. Again, nobody who is not an expert is
> ever supposed to compile and install glibc because it is far too dangerous.
> Nobody with some understand needed more information so far, otherwise
> documentation would have been contributed. If you want to describe in detail
> how the installation process works feel free to come up with a patch. But the
> process itself (configure etc) is fine and don't expect anyone else to compare
> about this.
I actually have an idea how it's working, and yes LDFLAGS are used at link time
and not at runtime.
However, I also set LD_LIBRARY_PATH to point to the directories with .so files,
and in this particular case it points to the directory with library in question.
Now, let's stop talking about experts - in
http://sourceware.org/bugzilla/show_bug.cgi?id=10062
I have already established that 'configure' doesn't guess target as it should,
and I have established that the INSTALL file says nothing about the need to
guide 'configure'.
Were 'configure' and INSTALL files written by experts ?
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WORKSFORME |
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.