Re: [i386] Why g++ _always_ link an executable with libm.so?
Denis Zaitsev <[email protected]>
| Newsgroups | gmane.linux.gcc,gmane.comp.gcc.devel |
|---|---|
| Message-ID | <[email protected]> |
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? - To unsubscribe from this list: send the line "unsubscribe linux-gcc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html