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]
Other format: [Raw text]

Re: Advice requested: how big can we be?


 > From: Alexandre Oliva <aoliva@redhat.com>
 > 
 > On Sep 19, 2003, "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> wrote:
 > 
 > >     I have an unconfirmed suspicion that this second one is an issue
 > >     with sharing config.cache among all of the target libraries.
 > 
 > Can't be.  It's more likely a bug in some target library that
 > incorrectly passes LD down to multilibs.  LD may have to have a
 > different value for different multilibs, and several target libs
 > already know to pass the original LD down.
 > 
 > Hmm...  libstdc++-v3/configure says:
 > 
 > ### am handles this now?  ORIGINAL_LD_FOR_MULTILIBS=$LD
 > 
 > Nope, AFAIK it doesn't.  Looks like taking this out may have caused
 > the problem.

Funny, I was just tracking the history of ORIGINAL_LD_FOR_MULTILIBS
this morning because I recalled you solved something similar to the
current problem a while ago.  I found these links:
http://gcc.gnu.org/ml/gcc-patches/2002-05/msg00714.html
http://gcc.gnu.org/ml/gcc-patches/2003-02/msg01640.html

I suppose Phil deleted this when he converted libstdc++-v3 to autoconf
2.5?  I'm not fluent in v2.5, what needs to be put back and where?

--
Kaveh R. Ghazi			ghazi@caip.rutgers.edu


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