This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: V3: Problem on Solaris


On Nov 12, 2000, Mark Mitchell <mark@codesourcery.com> wrote:

> That sounds plausible.  It's not actually abstractly correct, though:
> there could be other libraries that we *do* need to link in.

I see.

>     # $CC -shared without GNU ld will not create a library from C++
>     # object files and a static libstdc++, better avoid it by now

> (Here $CC is known to be GCC.)

> That comment doesn't really make any sense.  If you're using C++
> object files, you always have to link with the C++ compiler; I bet
> this predates the multi-language libtool.

It does.  In fact, now I recall I do know of a work-around for this
problem.  If GCC is new enough, one may use -mimpure-text when
creating the shared library on Solaris.  But, in the multi-language
libtool, this is no longer needed.  We can safely go back to using
$CC, since libtool does check whether libraries explicitly listed in
the command line are static; it only missed libstdc++ because it was
implicitly linked in.

> I'm going to stick with changing ltcf-c.sh for now -- but I'm happy
> to have you do something different later if you think that will be
> better.

That will be fine.  Please Cc: the patch to libtool-patches@gnu.org

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]