Archaic wrote:
On Thu, May 26, 2005 at 01:44:10PM -0700, Jim Gifford wrote:
What about when you build on x86 for a different platform then chroot
is not an option at all. That's the reason we added that to the book.
For that I would suggest a livecd. How exotic must we get?
Would
On Thu, May 26, 2005 at 01:44:10PM -0700, Jim Gifford wrote:
>
> What about when you build on x86 for a different platform then chroot
> is not an option at all. That's the reason we added that to the book.
For that I would suggest a livecd. How exotic must we get?
--
Archaic
Want control, edu
Matthew Burgess wrote these words on 05/26/05 16:46 CST:
> Jeremy Huntwork wrote:
>
>>Keep it all on the same machine, but
>> change the chroot to a reboot section so that you can reboot into a
>>kernel that supports 64-bit. Where there is need to do that all on
>>another machine (an entirely d
Jeremy Huntwork wrote:
Keep it all on the same machine, but
change the chroot to a reboot section so that you can reboot into a
kernel that supports 64-bit. Where there is need to do that all on
another machine (an entirely different arch family) you get pointed
toward a hint.
Am I reading
El Jueves, 26 de Mayo de 2005 23:03, Jim Gifford escribió:
> Matt, that was one of the purposes of the cross-lfs was the
> multi-architecture build, the reboot section is needed. I have it
> working and have been making the changes. It's just at the reboot point
> where there seems to be an issue.
Jim Gifford wrote:
Matt, that was one of the purposes of the cross-lfs was the
multi-architecture build, the reboot section is needed. I have it
working and have been making the changes. It's just at the reboot point
where there seems to be an issue.
I think that's what he was saying - Keep i
Matthew Burgess wrote:
Then the book should point you at a 'how to move target files from
host to target where target!=host' style hint. Although the cross-lfs
book is an enabler for cross-lfsing, I'm not convinced that the
majority of our readers will in actual fact be cross-building their
Jon Ringle wrote:
On Thursday 26 May 2005 16:44, Jim Gifford wrote:
What about when you build on x86 for a different platform then chroot is
not an option at all. That's the reason we added that to the book.
I am working with the cross-lfs scripts to target an arm processor from an x86
host
On Thursday 26 May 2005 16:44, Jim Gifford wrote:
> What about when you build on x86 for a different platform then chroot is
> not an option at all. That's the reason we added that to the book.
I am working with the cross-lfs scripts to target an arm processor from an x86
host. I certainly can't
Jeremy Huntwork wrote:
This one, IMHO is the worst possible option to support in the book.
The others of course, too, have drawbacks, but this one is by far the
worst. I would rather see the book *only* have a chroot path than have
a tar/copy files for your new system.
In fact, the more I
El Jueves, 26 de Mayo de 2005 22:11, Archaic escribió:
> On Thu, May 26, 2005 at 04:05:41PM -0400, Jeremy Huntwork wrote:
> > After spending some time on the "reboot" section, I think it's a mistake
> > to include any of that extra stuff in the book. Esp. when it still seems
> > that more will be t
On Thu, May 26, 2005 at 04:05:41PM -0400, Jeremy Huntwork wrote:
>
> After spending some time on the "reboot" section, I think it's a mistake
> to include any of that extra stuff in the book. Esp. when it still seems
> that more will be taking the chroot path anyway.
Exactly what I was saying..
Archaic wrote:
In an attempt to get this info both archived, and presented to the
larger community, I am writing up a synopsis of ideas that have been
floating around on IRC as to how to handle the chroot/reboot phase of
the cross-lfs book. I will list them and give a brief pro/con for each
as I
13 matches
Mail list logo
