This is the mail archive of the
mailing list for the GCC project.
Re: PATCH: PR other/17783: Top level configure doesn't support sharedlibraries enabled by default
- From: Mark Mitchell <mark at codesourcery dot com>
- To: "H. J. Lu" <hjl at lucon dot org>
- Cc: Geert Bosch <bosch at gnat dot com>, Andrew Pinski <pinskia at physics dot uc dot edu>, gcc mailing list <gcc at gcc dot gnu dot org>, gcc-patches at gcc dot gnu dot org
- Date: Tue, 02 Nov 2004 14:14:29 -0800
- Subject: Re: PATCH: PR other/17783: Top level configure doesn't support sharedlibraries enabled by default
- Organization: CodeSourcery, LLC
- References: <4185C537.email@example.com> <75F041F6-2BC9-11D9-8250-000A95D692F4@physics.uc.edu> <B1785B27-2C1E-11D9-B4B0-000A959A128E@gnat.com> <20041101163339.GA5030@lucon.org> <418722CB.firstname.lastname@example.org> <20041102175109.GA27332@lucon.org> <20041102181257.GA28078@lucon.org>
H. J. Lu wrote:
On Tue, Nov 02, 2004 at 09:51:09AM -0800, H. J. Lu wrote:I'm not happy about a patch like this, to the toplevel configury, at the
last minute. You might cause undesirable consequences on lots of other
On Mon, Nov 01, 2004 at 10:01:47PM -0800, Mark Mitchell wrote:
enable_shared in top level is only used for setting up proper
http://gcc.gnu.org/ml/gcc-patches/2004-10/msg00795.htmlThis last one, at least, is clearly wrong.
You're now defaulting to --enable-shared, even on systems that may not
support shared libraries at all.
LD_LIBRARY_PATH. If systems don't support shared libraries, setting
LD_LIBRARY_PATH won't affect anything. If we wants to prevent it
leaking down, we can change it to set_lib_path.
Here is the updated patch.
I'm not happy about not following the IA64 libunwind ABI, either, but
neither did GCC 3.4.2, and the world hasn't stopped spinning.
I would like someone other than you to test your patch on an IA64
GNU/Linux system without system libunwind, on an IA64 GNU/Linux system
with system libunwind, and on other non-IA64, non-GNU/Linux systems as
well. Please send reports directly to me.
I would also like to know which systems do not have a working system
libunwind installed. Do the most recent versions from Debian, Red Hat,
SuSE, etc. have system libunwind? In other words, what systems are we
likely to actually show this problem?