From: Thorsten Glaser <tg@mirbsd.de>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Nicholas Bellinger <nab@linux-iscsi.org>,
Greg Ungerer <gerg@uclinux.org>,
linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org,
target-devel@vger.kernel.org
Subject: Re: [m68k] in modpost: "strlen" [iscsi_target_mod.ko] undefined! (and others)
Date: Sun, 1 Jan 2012 23:45:51 +0000 (UTC) [thread overview]
Message-ID: <Pine.BSM.4.64L.1201012342490.20109@herc.mirbsd.org> (raw)
In-Reply-To: <20120101233931.GA25837@elie.hsd1.il.comcast.net>
Jonathan Nieder dixit:
>Could you suggest a patch to arch/m68k/Makefile to do that?
No, I patched it in debian/config/m68k/defines instead.
I’d rather know why upstream doesn’t use -ffreestanding on
_all_ architectures. A kernel is _not_ a hosted environment,
and GCC is right to bring in problems like this.
> Then drop -ffreestanding from the main Makefile because it isn't
> needed anymore and implies -fno-builtin, which is wrong now.
This is wrong, GCC builtins are only valid on hosted platforms,
not on freestanding platforms. (Nobody prevents GCC from using
a memcpy builtin that uses, say, SSE instructions, which must
not be used inside kernel code, for an example on a better-known
architecture.) A kernel must always be compiled freestanding,
as do bootloaders. At least since the advent of gcc 3.[34].
bye,
//mirabilos
--
“It is inappropriate to require that a time represented as
seconds since the Epoch precisely represent the number of
seconds between the referenced time and the Epoch.”
-- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2
next prev parent reply other threads:[~2012-01-01 23:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111116181424.14920.7730.reportbug@ara5.mirbsd.org>
[not found] ` <Pine.BSM.4.64L.1111301751500.12725@herc.mirbsd.org>
[not found] ` <CAMuHMdW8t8Q7OqxJM602iLG4aSv1KMTY-fhiGS7hyy8xBReh1A@mail.gmail.com>
[not found] ` <Pine.BSM.4.64L.1112181741430.856@herc.mirbsd.org>
2011-12-18 19:33 ` Bug#648996: linux-2.6: FTBFS " Thorsten Glaser
2012-01-01 23:12 ` Thorsten Glaser
2012-01-01 23:39 ` Jonathan Nieder
2012-01-01 23:45 ` Thorsten Glaser [this message]
2012-01-02 0:10 ` Jonathan Nieder
2012-01-02 0:19 ` Thorsten Glaser
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=Pine.BSM.4.64L.1201012342490.20109@herc.mirbsd.org \
--to=tg@mirbsd.de \
--cc=gerg@uclinux.org \
--cc=jrnieder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=target-devel@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
all inboxes | Powered by JetHome®