On Sun, 2010-01-03 at 17:07 -0500, Mikie wrote:
> I still think the book is for advanced people as it stands now.
100% correct. It *is* for advanced people, quite intentionally. It's
intended for those people who are interested in understanding things
like how the toolchain works, how everything f
Felipe Sá wrote:
> When I try to configure GRUB-0.97 in section 8.4 of LFS 6.5 I get an
> error saying that C compiler cannot create executables. Other previous
> compiles were fine. Can anyone help?
LFS-6.5 uses grub legacy and that can't be built on an x86_64 system.
"This package will only b
When I try to configure GRUB-0.97 in section 8.4 of LFS 6.5 I get an
error saying that C compiler cannot create executables. Other previous
compiles were fine. Can anyone help?
Configure outputs:
--
root:/sources/grub-0.97#
Mikie wrote these words on 01/03/10 16:07 CST:
> I may be new to Linux (BTW: I have built LFS two other times) but I do know
> how to teach and reach people.
> This is a separate skill set independent of the subject matter one is trying
> to teach.
>
> I still think the book is for advanced peop
Mikie wrote:
> I still think the book is for advanced people as it stands now.
Yes, It is intended to be. Did you read the Preface?
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information p
On Saturday 02 January 2010 10:39:38 Mikie wrote:
> *** These critical programs are missing or too old: as ld
> *** Check the INSTALL file for required versions.
>
It looks like you may have missed the section about the host system's
requirements. Could you confirm that you have the binutils pac
On Sunday 03 January 2010 15:10:47 Trent Shea wrote:
> On Sunday 03 January 2010 15:08:30 Trent Shea wrote:
> > On Saturday 02 January 2010 10:39:38 Mikie wrote:
> > > *** These critical programs are missing or too old: as ld
> > > *** Check the INSTALL file for required versions.
> >
> > It looks
On Sunday 03 January 2010 15:08:30 Trent Shea wrote:
> On Saturday 02 January 2010 10:39:38 Mikie wrote:
> > *** These critical programs are missing or too old: as ld
> > *** Check the INSTALL file for required versions.
>
> It looks like you may have missed the section about the host system's
> r
Mikie wrote:
>> What is the difference using another user and substituting that
>> username elsewhere in the book?
>
> Probably none, but using a different username has not been tested.
> What I can say for certain is that although you said you had been
> using the username 'ubuntu', the environ
> I don't see why the authors of LFS don¹t create a liveCD with the independent
> tool chain ready to go and delete Ch 5.
Because this would remove a significant part of the education value, in
terms of providing a context for understanding how to abstract and isolate a
build chain from a given ho
> What is the difference using another user and substituting that username
> elsewhere in the book?
Probably none, but using a different username has not been tested.
What I can say for certain is that although you said you had been
using the username 'ubuntu', the environment for that user did n
> All I want is to build a minimal Linux system for embedded development.
> Why is LFS so complicated?
> Is there another alternative?
>
> I don't see why the authors of LFS don’t create a liveCD with the independent
> tool chain ready to go and delete Ch 5.
> Why put a newbie like me thru all thi
Jan-Christoph Bornschlegel wrote:
> Am Sonntag 03 Januar 2010 19:38:03 schrieb Andrew Benton:
>>> The name "lfs:lfs" doesn't matter, you're free to change. It just has to
>>> be a user in the chroot system.
>> No, root does the chroot part
>
> Erm, sorry, not precise enough.
> What I meant is that
Am Sonntag 03 Januar 2010 19:38:03 schrieb Andrew Benton:
> > The name "lfs:lfs" doesn't matter, you're free to change. It just has to
> > be a user in the chroot system.
>
> No, root does the chroot part
Erm, sorry, not precise enough.
What I meant is that the user "lfs" must come from $LFS/etc/p
Andrew Benton wrote:
> The point about creating the user lfs is to ensure that you've set up
> the environment and its variables correctly.
That's really right. The lfs user (or whatever name you choose) needs
to have some environment variables set, but we chose the methodology to
also saniti
On 03/01/10 15:53, Jan-Christoph Bornschlegel wrote:
> Am Sonntag 03 Januar 2010 16:36:58 schrieb Mikie:
>> What is the difference using another user and substituting that username
>> elsewhere in the book? Is the LFS user hardcoded in the kernel with special
>> privileges?
> *ROTFL*
> Did you noti
2010/1/3 Mikie :
>>Then you need to rm -rf /tools/*, go back to the part where you create
>>the lfs user and its environment, and do everything from that point on.
>
> What is the difference using another user and substituting that username
> elsewhere in the book?
Probably none, but using a diff
On 1/3/10 7:36 AM, "Mikie" wrote:
>
> What is the difference using another user and substituting that username
> elsewhere in the book?
> Is the LFS user hardcoded in the kernel with special privileges?
As long as you're consistent (and changing the name for no particular reason
makes it more di
Am Sonntag 03 Januar 2010 16:36:58 schrieb Mikie:
> What is the difference using another user and substituting that username
> elsewhere in the book? Is the LFS user hardcoded in the kernel with special
> privileges?
*ROTFL*
Did you notice where your kernel comes from? ;)
The name "lfs:lfs" doesn'
You've lost me. Are you not using the 6.5 book ?
(sections 4.4, 5.5, 5.6, 5.7)
ĸen
--
[K. Mike Bradley]
Yes of course.
I am using a LiveCD Ubuntu 9.10 desktop version as my host to make LFS.
I boot to this and then:
sudo passwd ubuntu
1234
1234
sudo apt-get install ssh
Then I logon as user
>Then you need to rm -rf /tools/*, go back to the part where you create
>the lfs user and its environment, and do everything from that point on.
What is the difference using another user and substituting that username
elsewhere in the book?
Is the LFS user hardcoded in the kernel with special pr
21 matches
Mail list logo
