From: Denis Zaitsev <zzz@anda.ru>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: gcc@gcc.gnu.org, linux-gcc@vger.kernel.org
Subject: Re: [i386] Why g++ _always_ link an executable with libm.so?
Date: Thu, 6 Jan 2005 03:55:33 +0500 [thread overview]
Message-ID: <20050106035533.N1437@natasha.ward.six> (raw)
In-Reply-To: <m3ekgz8pim.fsf@uniton.integrable-solutions.net>; from gdr@integrable-solutions.net on Wed, Jan 05, 2005 at 11:44:33PM +0100
On Wed, Jan 05, 2005 at 11:44:33PM +0100, Gabriel Dos Reis wrote:
> Denis Zaitsev <zzz@anda.ru> writes:
>
> | > | Ok, but do we force users to use libm every time libc is used?
> | >
> | > What is libc? How do you define it?
> |
> | I assume GLIBC, of course. For x86, but I don't know either this
> | matters.
>
> That is a very narrow definition; however, are you claiming that the
> mathematical functions are not part of GLIBC?
Of course no, I'm not.
prev parent reply other threads:[~2005-01-05 22:55 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
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 [this message]
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=20050106035533.N1437@natasha.ward.six \
--to=zzz@anda.ru \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=linux-gcc@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).