On Sat, Feb 07, 2009 at 10:54:32PM +0100, Robert Millan wrote:
> On Tue, Jan 27, 2009 at 08:56:59PM +0100, Christian Franke wrote:
> >
> > Robert: Patch is IMO GTG.
>
> Ok. If noone objects I'll check it in soon.
Committed.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us.
On Tue, Jan 27, 2009 at 08:56:59PM +0100, Christian Franke wrote:
>
> Robert: Patch is IMO GTG.
Ok. If noone objects I'll check it in soon.
--
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 y
On Tue, Jan 27, 2009 at 06:33:47PM +0100, Javier Martín wrote:
>
> So you propose --target to be reused like this (a PS3 building GRUB2 for
> an amd64 BIOS PC with Linux) :
> ./configure --build=ppc64-linux --host=x86_64-linux-gnu --target=i686-pc
> ^--compiling system ^--tools syste
On Mon, Jan 26, 2009 at 08:57:10PM +0100, Christian Franke wrote:
> But even if GRUB itself is build for some $target_cpu-$target_vendor
> (i386-pc), the target_os is not useless if cross-compilation support is
> desired:
>
> - GRUB tools like grub-setup are build for the target_os
> - Package s
Javier Martín wrote:
El mar, 27-01-2009 a las 20:56 +0100, Christian Franke escribió:
Is building a bare 'no-OS' compiler supported by the upstream GCC sources?
Probably a too strict prerequisite for building GRUB.
I can't vouch so for all possible environments, but I can say that
"cle
El mar, 27-01-2009 a las 20:56 +0100, Christian Franke escribió:
> Javier Martín wrote:
> > El mar, 27-01-2009 a las 18:21 +0100, Christian Franke escribió:
> >
> >> Javier Martín wrote:
> >>
> Unfortunately, gcc has no '-fno_os' option to specify the bare CPU as
> target.
>
Javier Martín wrote:
El mar, 27-01-2009 a las 18:21 +0100, Christian Franke escribió:
Javier Martín wrote:
Unfortunately, gcc has no '-fno_os' option to specify the bare CPU as
target.
Might -ffreestanding be what you are looking for?
The option '-ffreestandin
El mar, 27-01-2009 a las 18:21 +0100, Christian Franke escribió:
> Javier Martín wrote:
> >> Unfortunately, gcc has no '-fno_os' option to specify the bare CPU as
> >> target.
> >>
> >
> > Might -ffreestanding be what you are looking for?
> >
> >
>
> The option '-ffreestanding' is the sam
El mar, 27-01-2009 a las 18:51 +0200, Vesa Jääskeläinen escribió:
> Javier Martín wrote:
> > A, say, AMD64 Linux cross compiler hosted on x86 Cygwin would have
> > $build=i686-pc-cygwin and $host=amd64-linux-gnu. Thus, no conflict ought
> > to arise even with cross compilation enabled.
> >
> > AFA
Javier Martín wrote:
Unfortunately, gcc has no '-fno_os' option to specify the bare CPU as
target.
Might -ffreestanding be what you are looking for?
The option '-ffreestanding' is the same as '-fno-hosted'.
According to gcc (4.3.1) source, '-fno-hosted' clears variable
'flag_hosted
Javier Martín wrote:
> A, say, AMD64 Linux cross compiler hosted on x86 Cygwin would have
> $build=i686-pc-cygwin and $host=amd64-linux-gnu. Thus, no conflict ought
> to arise even with cross compilation enabled.
>
> AFAIK, the full power of $build+$host+$target only matters when building
> _compi
Hi GRUB devs,
El lun, 26-01-2009 a las 20:57 +0100, Christian Franke escribió:
> Robert Millan wrote:
> > Hi,
> >
> > Based on the description of host/target triplets in configure.ac:
> >
> > dnl build -- the environment for building GRUB
> > dnl host -- the environment for running utilities
Robert Millan wrote:
Hi,
Based on the description of host/target triplets in configure.ac:
dnl build -- the environment for building GRUB
dnl host -- the environment for running utilities
dnl target -- the environment for running GRUB
it seems that target_os is an oxymoron. There's n
Hi,
Based on the description of host/target triplets in configure.ac:
dnl build -- the environment for building GRUB
dnl host -- the environment for running utilities
dnl target -- the environment for running GRUB
it seems that target_os is an oxymoron. There's no OS in the environmen
14 matches
Mail list logo
