From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Report: compil error on OSX for target=i386
Date: Tue, 8 Sep 2009 16:41:27 +0200 [thread overview]
Message-ID: <20090908144127.GA13674@thorin> (raw)
In-Reply-To: <BDF694BA-C88F-4D4B-BDCB-FF4D6BEBEFE2@zetam.org>
On Sun, Sep 06, 2009 at 08:56:59PM +0200, Yves Blusseau wrote:
>
> Bad news grub not compiled on a GCC 4.4.1 from MacPorts:
>
> gcc-mp-4.4 -Iloader/i386 -I./loader/i386 -I. -I./include -I./include -
> Wall -W -Wall -W -Wshadow -Wpointer-arith -Wmissing-prototypes
> -Wundef -Wstrict-prototypes -g -Os -falign-jumps=1 -falign-loops=1
> -falign-functions=1 -fno-dwarf2-cfi-asm -DAPPLE_CC=1 -m32
> -fno-stack-protector -mno-stack-arg-probe -fno-builtin -mrtd -mregparm=3
> -m32 -MD -c -o linux_mod-loader_i386_linux.o loader/i386/linux.c
> 20:16loader/i386/linux.c: In function 'grub_linux_boot':
> 20:16loader/i386/linux.c:546: error: can't find a register in class
> 'BREG' while reloading 'asm'
> 20:16loader/i386/linux.c:546: error: 'asm' operand has impossible
> constraints
> 20:16make: * [linux_mod-loader_i386_linux.o] Error 1
>
> MacPorts don't use specific patch to build gcc so i think the behavior
> is coded somewhere in the gcc source code.
I guess that's the implicit -fPIC you mentioned on IRC?
Does -fno-PIC help?
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-09-08 14:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 14:34 Report: compil error on OSX for target=i386 Yves Blusseau
2009-08-08 14:44 ` Bean
2009-08-08 14:47 ` Vladimir 'phcoder' Serbinenko
2009-08-08 14:53 ` Bean
2009-08-10 11:41 ` Robert Millan
2009-08-22 18:00 ` Vladimir 'phcoder' Serbinenko
2009-08-23 11:00 ` Robert Millan
2009-08-23 11:10 ` Vladimir 'phcoder' Serbinenko
2009-08-28 17:29 ` Vladimir 'phcoder' Serbinenko
2009-08-31 21:10 ` Yves Blusseau
2009-09-01 11:46 ` Robert Millan
2009-09-03 21:01 ` Yves Blusseau
2009-09-04 11:48 ` Robert Millan
2009-09-05 11:47 ` Yves Blusseau
2009-09-05 20:26 ` Robert Millan
2009-09-03 21:33 ` Vladimir 'phcoder' Serbinenko
2009-09-04 11:59 ` Robert Millan
2009-09-05 13:17 ` Michal Suchanek
2009-09-05 20:31 ` Robert Millan
2009-09-05 20:59 ` Vladimir 'phcoder' Serbinenko
2009-09-06 4:55 ` Yves Blusseau
2009-09-06 14:54 ` Robert Millan
2009-09-06 16:30 ` Yves Blusseau
2009-09-06 17:17 ` Vladimir 'phcoder' Serbinenko
2009-09-06 17:51 ` Yves Blusseau
2009-09-06 18:56 ` Yves Blusseau
2009-09-06 19:07 ` Felix Zielcke
2009-09-08 14:41 ` Robert Millan [this message]
2009-09-08 17:38 ` Yves Blusseau
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=20090908144127.GA13674@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.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.