On Jan 12, 2000, Thomas Tanner <[EMAIL PROTECTED]> wrote:
> On 12-Jan-2000 R. Bernstein wrote:
>> To recap: Mesa 3.1 shared libraries built via gcc on Solaris (and
>> probably other non glibc which means probably anything other than
>> HURD, Free/NetBSD or Linux) fail because they are linked via ld rather
>> than gcc.
> AFAIK this is a known libtool bug.
Yup. The problem is not exactly the fact that `ld' is used. The
problem is that GCC's crt init and end object files, that handle
dynamic initializers, are not linked in by libtool. Since they're not
needed for C, which is the only language the current libtool
officially supports, this is not much of a problem.
The multi-language libtool, currently under development by Ossama
Othman, will address this and a couple of other problems.
The (main?) reason why libtool uses `ld' on Solaris, when gcc doesn't
use GNU ld, is that, if libstdc++ is not available as a shared
library, linking another shared library with `libtool g++ -o libnew.la
...' would fail with a complaint from `ld' that some code imported
from libstdc++ needed relocation. So, if you don't mind if this fails
for the users of your code, you may just hack ltconfig so that it
always uses $CC for linking shared libraries, and it should be fine.
In fact, we might even do this for libtool 1.3.5, if it is ever
released, since this problem only affects g++ with static libstdc++,
and C++ is not officially supported anyway.
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{lsd.ic.unicamp.br,guarana.{org,com}} aoliva@{acm,computer}.org
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them
_______________________________________________
Mesa-bug maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-bug
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
