Richard Bland RBland at PeopleSupport.com
Tue Oct 3 15:33:51 PDT 2000

>what went wrong then?
It's a long story... I was going to post an answer to my previous thread
("LFS 2.4 - Hang on 1st reboot") detailing what went wrong (for the

>Perhaps 400MB would be best <snip>
LFS is going onto a 400MB HDD :(

Actually, I cheated and finally compiled it all in a faux LFS mount point,
actually just another dir on larger disk. I then stripped and tarred the
result onto the small IDE disk and threw that in the old 486, booted off a
floppy and off I went (or so I thought...)

I'll chroot into my (larger) 'virtual drive' and leave it to re-build libc
tonight. Hopefully, it'll behave this time.


Rich B

-----Original Message-----
From: Gerard Beekmans [mailto:gerard at linuxfromscratch.org]
Sent: Tuesday, October 03, 2000 2:55 PM
To: lfs-discuss at linuxfromscratch.org
Subject: Re: ld-2.1.3.so

On Tue, 03 Oct 2000, you wrote:

> > Can anyone tell me where the above lib is created during the LFS 2.4
> process? I'm guessing at the glibc compile.


> Either this or libc is corrupt on my target LFS build. Replacing them with
> my RedHat 6.2 version fixed the issue, but I'd like to recompile for
> cleanliness.

what went wrong then?

You can recompile Glibc inside chroot. that should work just fine.

> Also, how much space _do_ you need to the libc compile. I ran out with
> 260MB spare :(

Can't remember exactly, but have roughly 350MB available. Perhaps 400MB
be best so you're sure you won't run out of space

Gerard Beekmans

-*- If Linux doesn't have the solution, you have the wrong problem -*-

Unsubscribe: send email to lfs-discuss-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfromscratch.org/pipermail/lfs-dev/attachments/20001003/50981440/attachment.html>

More information about the lfs-dev mailing list