This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: repost: libg++ won't build on alphaev56-dec-osf4.0d
- To: law at cygnus dot com
- Subject: Re: repost: libg++ won't build on alphaev56-dec-osf4.0d
- From: Alexandre Oliva <oliva at dcc dot unicamp dot br>
- Date: 07 Jan 1999 06:33:42 -0200
- Cc: manfred at s-direktnet dot de, Manfred dot Hollstein at ks dot sel dot alcatel dot de, egcs-bugs at cygnus dot com
- References: <7593.915696681@hurl.cygnus.com>
On Jan 7, 1999, Jeffrey A Law <law@hurl.cygnus.com> wrote:
> In message <orlnjffrjk.fsf@araguaia.dcc.unicamp.br>you write:
>> I'm not talking about arbitrary libraries, I'm talking about the way
>> we build libstdc++ only. It doesn't have to include symbols from
>> libgcc because any program linked with libstdc++ should link libgcc in
>> too.
> No, not necessarily. In fact, I've run into this problem before. Folks
> had a C program which did a shl_load on a bunch of C++ shared libraries,
> including libstdc++.
Ugh! Well, in this case, I think the only way out is to arrange for
controlled symbol exporting. It doesn't really have to be portable
across platforms, since it's just an additional argument to the
libstdc++ build command. But I should not that, with libtool, this
could be made in a portable way. :-)
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva aoliva@{acm.org}
oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org}
Universidade Estadual de Campinas, SP, Brasil