From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: grub-devel@gnu.org
Cc: Philipp Kern <pkern@debian.org>,
457491@bugs.debian.org, Robert Millan <rmh@aybabtu.com>
Subject: Re: Fwd: grub2: FTBFS on powerpc (__floatundisf in ls is not defined)
Date: Sun, 13 Jan 2008 21:38:38 +0100 [thread overview]
Message-ID: <200801132138.39002.okuji@enbug.org> (raw)
In-Reply-To: <20080113201619.GA23454@thorin>
On Sunday 13 January 2008 21:16, Robert Millan wrote:
> On Sun, Jan 13, 2008 at 08:53:49PM +0100, Yoshinori K. Okuji wrote:
> > On Sunday 13 January 2008 13:19, Robert Millan wrote:
> > > This is becoming a nightmare. I think it's better if we just exclude
> > > symbols starting with __ from our checks. They aren't really meant for
> > > us to mess with.
> >
> > My original suggestion was that we could extract (required) symbols from
> > libgcc, and export them from the kernel. I think this can be automated.
>
> Yes, but what's the point? Doesn't libgcc already provide those symbols?
It does, but our kernel doesn't.
> The problem seems to be only with our checker scripts, not with linking
> itself.
>
> Unless I missed something of course..
From my point of view, ignoring all symbols starting with __ is a hack. I
prefer to resolve symbols in the Right Way.
Okuji
next prev parent reply other threads:[~2008-01-13 20:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071222194111.GA8254@durotan.0x539.de>
2007-12-25 9:32 ` Fwd: grub2: FTBFS on powerpc (__floatundisf in ls is not defined) Robert Millan
2007-12-25 10:29 ` Yoshinori K. Okuji
2007-12-25 10:52 ` Robert Millan
[not found] ` <20071225120612.GA16779@durotan.0x539.de>
2007-12-25 19:21 ` Robert Millan
2007-12-26 9:21 ` Robert Millan
2008-01-13 12:19 ` Robert Millan
2008-01-13 19:53 ` Yoshinori K. Okuji
2008-01-13 20:16 ` Robert Millan
2008-01-13 20:38 ` Yoshinori K. Okuji [this message]
2008-01-15 11:14 ` Marco Gerards
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=200801132138.39002.okuji@enbug.org \
--to=okuji@enbug.org \
--cc=457491@bugs.debian.org \
--cc=grub-devel@gnu.org \
--cc=pkern@debian.org \
--cc=rmh@aybabtu.com \
/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.