linux fan wrote:
> On 12/3/09, Mike McCarty wrote:
>
>> You don't necessarily have to build on that machine. However,
>> I realize that may be part of the "challenge".
>
> Hmm, if LFS 6.5 cross compiles, could you build it on a fast machine
> for the slow machine and then put it on the slow machi
linux fan wrote:
> On 12/3/09, Mike McCarty wrote:
>
>> You don't necessarily have to build on that machine. However,
>> I realize that may be part of the "challenge".
>
> Hmm, if LFS 6.5 cross compiles, could you build it on a fast machine
> for the slow machine and then put it on the slow machi
On 12/3/09, Mike McCarty wrote:
> You don't necessarily have to build on that machine. However,
> I realize that may be part of the "challenge".
Hmm, if LFS 6.5 cross compiles, could you build it on a fast machine
for the slow machine and then put it on the slow machine with rsync or
something?
-
linux fan wrote:
> On 12/3/09, Simon Geard wrote:
>> Wow... if you *do* get a new LFS build running on that, I'd be curious
>> to know how long it took...
>
> My first guess is 11 days or so.
You don't necessarily have to build on that machine. However,
I realize that may be part of the "challeng
stosss wrote:
> Okay. I am starting over
I've been doing professional software development, including
high reliability and availability stuff (telecommmunications
equipment) since 1982. I had to restart my first build, too.
Moral: Don't feel badly about it. It's a lengthy process which
is easy to
Just a quick report back. Although a good night was had by all, Stormy
probably wasn't the right person to ask about Gnome technical issues as her
post is mainly managerial.
In reply to Jason she did say that Nautilus was very much in active
development and that The Gnome Foundation was very keen
On 12/3/09, Simon Geard wrote:
> Wow... if you *do* get a new LFS build running on that, I'd be curious
> to know how long it took...
My first guess is 11 days or so.
Calculating from:
http://www.linuxfromscratch.org/~sbu
MHz=100
one_sbu=5848
lfs_6_5_sbus=153
seconds=899422
time=10,9:50:22
--
ht
2009/12/3 stosss :
> I started over from scratch. I have captured log files of everything.
> I ran tests on everything and captured all those tests. Everything was
> going along nicely.
Apart from what others have said, I find it useful to log what got installed.
I think the book sketches this out
>On Thu, 3 Dec 2009 03:44:43 -0500
>stosss wrote:
>
> I started over from scratch. I have captured log files of everything.
> I ran tests on everything and captured all those tests. Everything was
> going along nicely.
>
> In chapter 6.4 I used:
>
> chroot "$LFS" /tools/bin/env -i \
> HOME=/
Okay. I am starting over
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
On Wed, 2009-12-02 at 23:21 -0500, Mykal Funk wrote:
> The machine has collected dust for the last 5 years. As it is a 486DX,
> it will take a couple days to see if your suggestions work. And yes, I
> think I left this one a bit too long. But I like a challenge. Thats why
> I bother with an old
Am Donnerstag 03 Dezember 2009 10:32:56 schrieb stosss:
> Did everything get built using
> GCC on the host? If it did then this entire LFS build is toast.
Well, if you compiled _anything_ successfully and don't have a working gcc in
your chroot environment, the question is, how could you use the
On 12/03/2009 04:32 AM, stosss wrote:
> On Thu, Dec 3, 2009 at 4:26 AM, Chris Staub wrote:
>> On 12/03/2009 04:15 AM, stosss wrote:
>>
>> If /usr/bin/gcc does not exist, then clearly GCC was not installed, most
>> likely because you missed "make install" in Chapter 6 GCC or somehow
>> skipped the
On Thu, Dec 3, 2009 at 4:26 AM, Chris Staub wrote:
> On 12/03/2009 04:15 AM, stosss wrote:
>> On Thu, Dec 3, 2009 at 4:10 AM, Chris Staub wrote:
>>> On 12/03/2009 04:04 AM, stosss wrote:
readelf: Error: '/usr/bin/gcc': No such file
So I probably did something wrong and changin
On 12/03/2009 04:15 AM, stosss wrote:
> On Thu, Dec 3, 2009 at 4:10 AM, Chris Staub wrote:
>> On 12/03/2009 04:04 AM, stosss wrote:
>>>
>>> readelf: Error: '/usr/bin/gcc': No such file
>>>
>>> So I probably did something wrong and changing my path when logging
>>> out and back revealed that?
>>
>>
On Thu, Dec 3, 2009 at 4:10 AM, Chris Staub wrote:
> On 12/03/2009 04:04 AM, stosss wrote:
>> On Thu, Dec 3, 2009 at 3:59 AM, Chris Staub wrote:
>>>
>>> readelf -l /usr/bin/gcc | grep interpret
>>>
>>> What's the result?
>>
>> readelf: Error: '/usr/bin/gcc': No such file
>>
>> So I probably did s
On 12/03/2009 04:04 AM, stosss wrote:
> On Thu, Dec 3, 2009 at 3:59 AM, Chris Staub wrote:
>>
>> readelf -l /usr/bin/gcc | grep interpret
>>
>> What's the result?
>
> readelf: Error: '/usr/bin/gcc': No such file
>
> So I probably did something wrong and changing my path when logging
> out and back
On Thu, Dec 3, 2009 at 3:59 AM, Chris Staub wrote:
> On 12/03/2009 03:44 AM, stosss wrote:
>> I started over from scratch. I have captured log files of everything.
>> I ran tests on everything and captured all those tests. Everything was
>> going along nicely.
>>
>> make: gcc: Command not found
>>
On 12/03/2009 03:44 AM, stosss wrote:
> I started over from scratch. I have captured log files of everything.
> I ran tests on everything and captured all those tests. Everything was
> going along nicely.
>
> make: gcc: Command not found
>
> What happened?
readelf -l /usr/bin/gcc | grep interpret
I started over from scratch. I have captured log files of everything.
I ran tests on everything and captured all those tests. Everything was
going along nicely.
In chapter 6.4 I used:
chroot "$LFS" /tools/bin/env -i \
HOME=/root TERM="$TERM" PS1='\u:\w\$ ' \
PATH=/bin:/usr/bin:/sbin:/usr/
20 matches
Mail list logo
