From: Robert Millan <rmh@aybabtu.com>
To: Philipp Kern <pkern@debian.org>
Cc: grub-devel@gnu.org, 457491@bugs.debian.org,
"Yoshinori K. Okuji" <okuji@enbug.org>
Subject: Re: Fwd: grub2: FTBFS on powerpc (__floatundisf in ls is not defined)
Date: Sun, 13 Jan 2008 13:19:03 +0100 [thread overview]
Message-ID: <20080113121903.GA25723@thorin> (raw)
In-Reply-To: <20071226092116.GA26341@thorin>
On Wed, Dec 26, 2007 at 10:21:16AM +0100, Robert Millan wrote:
> diff -ur grub2-1.95+20071101/include/grub/powerpc/libgcc.h grub2-1.95+20071101.new/include/grub/powerpc/libgcc.h
> --- grub2-1.95+20071101/include/grub/powerpc/libgcc.h 2007-07-21 23:32:24.000000000 +0000
> +++ grub2-1.95+20071101.new/include/grub/powerpc/libgcc.h 2007-12-26 08:42:49.000000000 +0000
> @@ -26,19 +26,12 @@
> void EXPORT_FUNC (__floatsidf) (void);
> void EXPORT_FUNC (__floatsisf) (void);
> void EXPORT_FUNC (__lshrdi3) (void);
> -void EXPORT_FUNC (__make_dp) (void);
> -void EXPORT_FUNC (__make_fp) (void);
> void EXPORT_FUNC (__muldf3) (void);
> void EXPORT_FUNC (__mulsf3) (void);
> -void EXPORT_FUNC (__pack_d) (void);
> -void EXPORT_FUNC (__pack_f) (void);
> void EXPORT_FUNC (__subdf3) (void);
> void EXPORT_FUNC (__subsf3) (void);
> -void EXPORT_FUNC (__thenan_df) (void);
> -void EXPORT_FUNC (__thenan_sf) (void);
> void EXPORT_FUNC (__trampoline_setup) (void);
> void EXPORT_FUNC (__truncdfsf2) (void);
> -void EXPORT_FUNC (__unpack_d) (void);
> -void EXPORT_FUNC (__unpack_f) (void);
> void EXPORT_FUNC (__floatdisf) (void);
> +void EXPORT_FUNC (__floatundisf) (void);
> void EXPORT_FUNC (__cmpdi2) (void);
>
> Is there any way we can preserve compatibility with gcc 3.x ? Perhaps obtain
> a list of symbols dynamicaly, but maybe this would bloat the kernel too much.
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.
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-01-13 12:27 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 [this message]
2008-01-13 19:53 ` Yoshinori K. Okuji
2008-01-13 20:16 ` Robert Millan
2008-01-13 20:38 ` Yoshinori K. Okuji
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=20080113121903.GA25723@thorin \
--to=rmh@aybabtu.com \
--cc=457491@bugs.debian.org \
--cc=grub-devel@gnu.org \
--cc=okuji@enbug.org \
--cc=pkern@debian.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 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.