This is the mail archive of the
libc-hacker@cygnus.com
mailing list for the glibc project.
Re: A patch for glibc 2.0/2.1
- To: Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>
- Subject: Re: A patch for glibc 2.0/2.1
- From: Zack Weinberg <zack@rabi.columbia.edu>
- Date: Fri, 22 Jan 1999 10:35:35 -0500
- cc: hjl@lucon.org (H.J. Lu), libc-hacker@cygnus.com (GNU C Library), drepper@cygnus.com (Ulrich Drepper)
On 22 Jan 1999 10:41:28 +0100, Andreas Schwab wrote:
>Zack Weinberg <zack@rabi.columbia.edu> writes:
>
>|> On Thu, 21 Jan 1999 11:42:19 -0800 (PST), H.J. Lu wrote:
>|> >> >
>|> >> >Oooops. Here is a patch for glibc 2.0 and 2.1. It will make
>|> >> >those functions weak extern in libc.so. Ulrich, could you please
>|> >> >check it in for both glibc 2.0 and 2.1? Thanks.
>|> >
>|> >On my second thought, Ulrich, please ignore this patch. We should
>|> >keep them in libc.so so that noone else has to define them. That
>|> >means libfoo.so made by
>|> >
>|> ># gcc -shared -o libfoo.so foo.cc -fPIC
>|> >
>|> >will work regardless if libstdc++.so is loaded or not.
>|>
>|> Then you have to disallow compiling libc with gcc 2.8. (I personally think
>|> this would be a good idea anyway.)
>
>That is completely STUPID.
Please explain.
zw