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: [i386] Why g++ _always_ link an executable with libm.so?


On Jan 5, 2005, at 5:09 PM, Denis Zaitsev wrote:

On Wed, Jan 05, 2005 at 01:21:23PM -0500, Andrew Pinski wrote:

On Jan 5, 2005, at 12:14 PM, Mike Hearn wrote:

I also find it strange (broken) that a c++ app that doesn't use any
libm
symbols is linked to it anyway. Why does it matter?

because libstdc++ might pull in libm symbols without the person knowing
he did. 

Ok.  But the question in general is not about that.  It is not a
problem that libm is NEEDED by libstdc++, but why this NEEDED leads to
the same NEEDED for the app?  Isn't the first depndency enough?


No, because some of libstdc++ code is in the headers, on some targets
have two level namespaces which causes this to be rejected.

-- Pinski

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