From: Bastian Blank <bastian@waldi.eu.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Arjan van de Ven <arjan@infradead.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: removing bcopy... because it's half broken
Date: Tue, 11 Jan 2005 11:10:38 +0100 [thread overview]
Message-ID: <20050111101010.GB27768@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0501091240550.2339@ppc970.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
On Sun, Jan 09, 2005 at 12:42:42PM -0800, Linus Torvalds wrote:
> On Sun, 9 Jan 2005, Christoph Hellwig wrote:
> > We're building with -ffreestanding now, so gcc isn't allowed to emit
> > any calls to standard library functions.
> Bzzt. It still emits calls to libgcc.
Yes. This means IMHO that the image and every module needs to link
against libgcc to include the required symbols. It is rather annoying to
see modules asking for libgcc symbols.
Bastian
--
It would be illogical to assume that all conditions remain stable.
-- Spock, "The Enterprise Incident", stardate 5027.3
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2005-01-11 10:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 19:23 removing bcopy... because it's half broken Arjan van de Ven
2005-01-09 19:39 ` Ralf Baechle
2005-01-09 20:03 ` Russell King
2005-01-09 20:19 ` Linus Torvalds
2005-01-09 20:33 ` Arjan van de Ven
2005-01-09 20:34 ` Christoph Hellwig
2005-01-09 20:42 ` Linus Torvalds
2005-01-11 10:10 ` Bastian Blank [this message]
2005-01-11 10:32 ` Arjan van de Ven
2005-01-11 16:10 ` Linus Torvalds
2005-01-09 23:38 ` Richard Henderson
2005-01-10 0:43 ` Adrian Bunk
2005-01-10 16:55 ` Matthias-Christian Ott
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=20050111101010.GB27768@wavehammer.waldi.eu.org \
--to=bastian@waldi.eu.org \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
--cc=torvalds@osdl.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 NNTP newsgroup(s).