[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Build C++ shared libs on HP-UX with aCC, not ld
From: |
Gary V . Vaughan |
Subject: |
Re: Build C++ shared libs on HP-UX with aCC, not ld |
Date: |
Mon, 6 Sep 2004 02:05:18 +0100 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Bob, Albert,
On 6 Sep 2004, at 01:33, Bob Friesenhahn wrote:
On Mon, 6 Sep 2004, Gary V.Vaughan wrote:
2004-09-05 Albert Chin-A-Young <address@hidden>
* m4/libtool.m4: Use the HP C++ compiler to build C++
shared libraries, not ld.
Before I apply this patch, I wonder: Is now the time to move
wholesale for using the C++ compiler for linking C++ libraries? In
addition to giving (hopefully) better reliability, we should be able
to drop all the code for trying to guess how the compiler will call
the linker if it turns out to work well...
Thoughts?
That would depend on if we know how to instruct the C++ compiler to
build a shared library for all supported environments. Is that the
case?
I doubt it. But we can certainly get a good approximation by looking
at how we link shared libs with the C compiler on that platform.
Perhaps a better plan is to show a warning for libtool alpha versions,
and convert each platform separately in due course. Say:
**** Warning: Libtool does not yet know whether it can safely link
**** $compiler shared libraries with $CC, attempting to link with $LD.
We can probably patch gcc and HP-UX's aCC right away, and then tackle
the others as convenient. Maybe we should even leave the warning on in
2.0 to solicit platform patches from libtool's C++ users?
Cheers,
Gary.
- --
Gary V. Vaughan ())_. address@hidden,gnu.org}
Research Scientist ( '/ http://tkd.kicks-ass.net
GNU Hacker / )= http://www.gnu.org/software/libtool
Technical Author `(_~)_ http://sources.redhat.com/autobook
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (Darwin)
iD8DBQFBO7fRFRMICSmD1gYRAhv0AJ0ZibAxt0LWL6wp1ZiT1kwUy/c5UQCfYTwK
V+wstExtTr6tHuq9GlEEwoI=
=7c9Y
-----END PGP SIGNATURE-----