Le 8 sept. 09 à 16:41, Robert Millan a écrit :
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 -Wmissin
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 -Wstr
Am Sonntag, den 06.09.2009, 20:56 +0200 schrieb Yves Blusseau:
> Le 6 sept. 09 à 16:54, Robert Millan a écrit :
>
> > On Sun, Sep 06, 2009 at 06:55:41AM +0200, Yves Blusseau wrote:
> >>
> >> Le 5 sept. 09 à 22:31, Robert Millan a écrit :
> >>
> >>> On Sat, Sep 05, 2009 at 03:17:58PM +0200, Michal
Le 6 sept. 09 à 16:54, Robert Millan a écrit :
On Sun, Sep 06, 2009 at 06:55:41AM +0200, Yves Blusseau wrote:
Le 5 sept. 09 à 22:31, Robert Millan a écrit :
On Sat, Sep 05, 2009 at 03:17:58PM +0200, Michal Suchanek wrote:
Still the time and space required to build GCC is much larger than
Le 6 sept. 09 à 19:17, Vladimir 'phcoder' Serbinenko a écrit :
checking whether target compiler is working... no
configure: error: cannot compile for the target
and if i look into the config.log it's because it use the default
apple
linker tool witch don't recognize some arguments:
configu
> checking whether target compiler is working... no
> configure: error: cannot compile for the target
>
> and if i look into the config.log it's because it use the default apple
> linker tool witch don't recognize some arguments:
>
> configure:5882: gcc-mp-4.4 -o conftest -Wall -W -Wshadow -Wpointe
Le 6 sept. 09 à 16:54, Robert Millan a écrit :
On Sun, Sep 06, 2009 at 06:55:41AM +0200, Yves Blusseau wrote:
Le 5 sept. 09 à 22:31, Robert Millan a écrit :
On Sat, Sep 05, 2009 at 03:17:58PM +0200, Michal Suchanek wrote:
Still the time and space required to build GCC is much larger than
On Sun, Sep 06, 2009 at 06:55:41AM +0200, Yves Blusseau wrote:
>
> Le 5 sept. 09 à 22:31, Robert Millan a écrit :
>
>> On Sat, Sep 05, 2009 at 03:17:58PM +0200, Michal Suchanek wrote:
>>>
>>> Still the time and space required to build GCC is much larger than
>>> that required for building grub. The
Le 5 sept. 09 à 22:31, Robert Millan a écrit :
On Sat, Sep 05, 2009 at 03:17:58PM +0200, Michal Suchanek wrote:
Still the time and space required to build GCC is much larger than
that required for building grub. The OS X platform is somewhat exotic
because it uses different object format and
On Sat, Sep 5, 2009 at 10:31 PM, Robert Millan wrote:
> On Sat, Sep 05, 2009 at 03:17:58PM +0200, Michal Suchanek wrote:
>>
>> Still the time and space required to build GCC is much larger than
>> that required for building grub. The OS X platform is somewhat exotic
>> because it uses different obj
On Sat, Sep 05, 2009 at 03:17:58PM +0200, Michal Suchanek wrote:
>
> Still the time and space required to build GCC is much larger than
> that required for building grub. The OS X platform is somewhat exotic
> because it uses different object format and non-gnu linker so it is
> more likely there
On Sat, Sep 05, 2009 at 01:47:52PM +0200, Yves Blusseau wrote:
>>
>> I assume you installed Apple's version of GCC. Can you try with an
>> official
>> GCC release?
>
> Yes, i have compiled on a true mac (Leopard 10.5.7) with the gcc-4.2.1
> version.
>
> I have tried to compil with a mac port o
2009/9/4 Robert Millan :
> On Thu, Sep 03, 2009 at 11:33:51PM +0200, Vladimir 'phcoder' Serbinenko wrote:
>> > It's much easier to make official GCC a build requirement. People hacking
>> > on GRUB source, or distributors (e.g. Fink) should have no problem with a
>> > dependency on GCC.
>> >
>> It
Le 4 sept. 09 à 13:48, Robert Millan a écrit :
On Thu, Sep 03, 2009 at 11:01:23PM +0200, Yves Blusseau wrote:
It's much easier to make official GCC a build requirement. People
hacking
on GRUB source, or distributors (e.g. Fink) should have no problem
with a
dependency on GCC.
So what you c
On Thu, Sep 03, 2009 at 11:33:51PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> > It's much easier to make official GCC a build requirement. People hacking
> > on GRUB source, or distributors (e.g. Fink) should have no problem with a
> > dependency on GCC.
> >
> It won't do a lot of difference fo
On Thu, Sep 03, 2009 at 11:01:23PM +0200, Yves Blusseau wrote:
>>
>> It's much easier to make official GCC a build requirement. People
>> hacking
>> on GRUB source, or distributors (e.g. Fink) should have no problem
>> with a
>> dependency on GCC.
>
> So what you can do because currently we ca
>>
>> Compil and work on OSX.
>>
>> Is it ok to commit it ?
>
> However, on our side, I'm not satisfied at all with accomodating to arbitrary
> limitations like this one. This seems like a slippery slope. If we do it
> now, what's the next one?
I agree that we shouldn't support a compiler if it r
Le 1 sept. 09 à 13:46, Robert Millan a écrit :
On Mon, Aug 31, 2009 at 11:10:17PM +0200, Yves Blusseau wrote:
What about following compromise:
diff --git a/loader/i386/linux.c b/loader/i386/linux.c
index 4144384..1380eb8 100644
--- a/loader/i386/linux.c
+++ b/loader/i386/linux.c
@@ -543,7 +543
On Mon, Aug 31, 2009 at 11:10:17PM +0200, Yves Blusseau wrote:
>>> What about following compromise:
>>> diff --git a/loader/i386/linux.c b/loader/i386/linux.c
>>> index 4144384..1380eb8 100644
>>> --- a/loader/i386/linux.c
>>> +++ b/loader/i386/linux.c
>>> @@ -543,7 +543,8 @@ grub_linux_boot (void)
What about following compromise:
diff --git a/loader/i386/linux.c b/loader/i386/linux.c
index 4144384..1380eb8 100644
--- a/loader/i386/linux.c
+++ b/loader/i386/linux.c
@@ -543,7 +543,8 @@ grub_linux_boot (void)
asm volatile ("lgdt %0" : : "m" (gdt_desc));
/* Enter Linux. */
- asm volatile
> What about following compromise:
> diff --git a/loader/i386/linux.c b/loader/i386/linux.c
> index 4144384..1380eb8 100644
> --- a/loader/i386/linux.c
> +++ b/loader/i386/linux.c
> @@ -543,7 +543,8 @@ grub_linux_boot (void)
> asm volatile ("lgdt %0" : : "m" (gdt_desc));
>
> /* Enter Linux. */
>> What about following compromise:
>> [...]
>
> I'm not sure what's the problem here. AFAIK inline assembly had this syntax
> with GCC 4.0 already. Did Apple cripple it in their version of GCC ?
Yes. They don't allow usage of %ebx/%rbx in constraints and clobbered registers
>
> --
> Robert Milla
On Sat, Aug 22, 2009 at 08:00:10PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> On Mon, Aug 10, 2009 at 1:41 PM, Robert Millan wrote:
> > On Sat, Aug 08, 2009 at 10:44:25PM +0800, Bean wrote:
> >> Hi,
> >>
> >> I also encounter this problem with apple gcc 4.0, the fix is to replace:
> >>
> >> asm
On Mon, Aug 10, 2009 at 1:41 PM, Robert Millan wrote:
> On Sat, Aug 08, 2009 at 10:44:25PM +0800, Bean wrote:
>> Hi,
>>
>> I also encounter this problem with apple gcc 4.0, the fix is to replace:
>>
>> asm volatile ("jmp *%2" : : "b" (0), "S" (real_mode_mem), "g"
>> (params->code32_start));
>>
>> W
On Sat, Aug 08, 2009 at 10:44:25PM +0800, Bean wrote:
> Hi,
>
> I also encounter this problem with apple gcc 4.0, the fix is to replace:
>
> asm volatile ("jmp *%2" : : "b" (0), "S" (real_mode_mem), "g"
> (params->code32_start));
>
> With:
> asm volatile ("movl %0, %%ecx" : : "m" (params->code
On Sat, Aug 8, 2009 at 10:47 PM, Vladimir 'phcoder'
Serbinenko wrote:
> On Sat, Aug 8, 2009 at 4:44 PM, Bean wrote:
>> Hi,
>>
>> I also encounter this problem with apple gcc 4.0, the fix is to replace:
>>
>> asm volatile ("jmp *%2" : : "b" (0), "S" (real_mode_mem), "g"
>> (params->code32_start));
>
On Sat, Aug 8, 2009 at 4:44 PM, Bean wrote:
> Hi,
>
> I also encounter this problem with apple gcc 4.0, the fix is to replace:
>
> asm volatile ("jmp *%2" : : "b" (0), "S" (real_mode_mem), "g"
> (params->code32_start));
>
> With:
> asm volatile ("movl %0, %%ecx" : : "m" (params->code32_start));
>
Hi,
I also encounter this problem with apple gcc 4.0, the fix is to replace:
asm volatile ("jmp *%2" : : "b" (0), "S" (real_mode_mem), "g"
(params->code32_start));
With:
asm volatile ("movl %0, %%ecx" : : "m" (params->code32_start));
asm volatile ("movl %0, %%esi" : : "m" (real_mode_mem));
28 matches
Mail list logo
