This is the mail archive of the gcc@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: A clue for the libstdc++ problem.


On Sun, Apr 01, 2001 at 03:21:07PM -0700, H . J . Lu wrote:
> 
> Please keep in mind that building the shared libstdc++ is a special
> case, just like building libc.so. You cannot use the normal C++ rules,
> just like we don't use the normal C rule for building libc.so.

Sure, but I think ltcf-* is the wrong layer to fix it at.  I think the
libstdc++ subdirectory configure.in is much more appropriate.  It
knows what's going on, the top level configury doesn't.

The patch I sent earlier today made it through bootstrap and is now
working on the check pass.

I'm wondering if we need to keep around the logic that determines
whether or not libstdc++, libjava, etc. are being built outside the
unified tree.

zw


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