From: Denis Zaitsev <zzz@anda.ru>
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: gcc@gcc.gnu.org, linux-gcc@vger.kernel.org,
Gabriel Dos Reis <gdr@integrable-solutions.net>
Subject: Re: [i386] Why g++ _always_ link an executable with libm.so?
Date: Wed, 5 Jan 2005 04:16:06 +0500 [thread overview]
Message-ID: <20050105041606.J1437@natasha.ward.six> (raw)
In-Reply-To: <51D8FCE4-5EA5-11D9-9A04-000A95D692F4@physics.uc.edu>; from pinskia@physics.uc.edu on Tue, Jan 04, 2005 at 06:06:51PM -0500
On Tue, Jan 04, 2005 at 06:06:51PM -0500, Andrew Pinski wrote:
>
> On Jan 4, 2005, at 5:59 PM, Denis Zaitsev wrote:
>
> > Ok, but do we force users to use libm every time libc is used? No, we
> > don't. Of course, we don't. And I emphasised the word 'always':
> > not _every_ routine from libstdc++ need libm, but it always
> > required...
>
> Then write a better collect2 which only links in the libraries which
> are needed and have it find the needed libraries without supplying
> the option to link the library (yes this is on the TODO page of gcc).
>
> Also note on some targets like darwin, libm is included in libsystem
> (aka
> libc) by default.
Ok, I'm not trying to criticize the way it implemented for now. I'm
trying to understand what happens now.
next prev parent reply other threads:[~2005-01-04 23:16 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 [this message]
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
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=20050105041606.J1437@natasha.ward.six \
--to=zzz@anda.ru \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=linux-gcc@vger.kernel.org \
--cc=pinskia@physics.uc.edu \
/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.