From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Denis Zaitsev <zzz@anda.ru>
Cc: Andrew Pinski <pinskia@physics.uc.edu>, Mike Hearn <mike@navi.cx>,
gcc@gcc.gnu.org, linux-gcc@vger.kernel.org
Subject: Re: [i386] Why g++ _always_ link an executable with libm.so?
Date: 05 Jan 2005 23:39:29 +0100 [thread overview]
Message-ID: <m3k6qr8pr2.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <20050106030954.K1437@natasha.ward.six>
Denis Zaitsev <zzz@anda.ru> writes:
| 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?
At this point I completely lose track of what your problem is and what
you're complaining about.
-- Gaby
next prev parent reply other threads:[~2005-01-05 22:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 22:01 [i386] Why g++ _always_ link an executable with libm.so? Denis Zaitsev
2005-01-04 22:05 ` Daniel Jacobowitz
2005-01-04 22:18 ` Denis Zaitsev
2005-01-04 22:30 ` Gabriel Dos Reis
2005-01-04 22:59 ` Denis Zaitsev
2005-01-04 23:06 ` Andrew Pinski
2005-01-04 23:16 ` Denis Zaitsev
2005-01-05 0:40 ` Gabriel Dos Reis
2005-01-05 17:14 ` Mike Hearn
2005-01-05 18:21 ` Andrew Pinski
2005-01-05 18:51 ` Mike Hearn
2005-01-05 18:48 ` Andrew Pinski
2005-01-05 19:10 ` Mike Hearn
2005-01-05 22:09 ` Denis Zaitsev
2005-01-05 22:16 ` Andrew Pinski
2005-01-05 22:30 ` Denis Zaitsev
2005-01-05 22:32 ` Andrew Pinski
2005-01-05 22:39 ` Gabriel Dos Reis [this message]
2005-01-05 0:38 ` Gabriel Dos Reis
2005-01-05 22:25 ` Denis Zaitsev
2005-01-05 22:30 ` Andrew Pinski
2005-01-05 22:44 ` Gabriel Dos Reis
2005-01-05 22:55 ` Denis Zaitsev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3k6qr8pr2.fsf@uniton.integrable-solutions.net \
--to=gdr@integrable-solutions.net \
--cc=gcc@gcc.gnu.org \
--cc=linux-gcc@vger.kernel.org \
--cc=mike@navi.cx \
--cc=pinskia@physics.uc.edu \
--cc=zzz@anda.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.