Yep, 'sudo make install' turned out to be my problem, too. I'm not sure if
I forgot to chown $LFS/tools or just used it out of habit, but either way
doing it again and following the directions correctly fixed the problem for
me. I didn't say anything because I also felt a little silly taking up
people's time with that. But if this error crops up for someone else again,
that's probably what caused it.


On Thu, Jan 23, 2014 at 12:59 PM, Enrique Larraia <[email protected]>wrote:

> Doh! In section 4.3 I overlooked the command:
>
> chown -v lfs $LFS/tools
>
> That's why I had to use 'sudo make install'' for $LFS/tools=
> /mnt/lfs/tools.
>
> I changed the owner of $LFS/tools to lfs user now. Sorry for wasting your
> time guys, but thanks anyway.
>
> kike
>
>
>
>
> 2014/1/22 Bruce Dubbs <[email protected]>
>
>> Enrique Larraia wrote:
>> > 2014/1/22 Pierre M.R. <[email protected]>
>> >
>> >> Enrique Larraia wrote:
>> >>> Not sure how to check this.
>> >> To be rude. I would edit gcc-build/libtool to add at line 1121: echo
>> $PATH
>> >>
>> >
>> > Yeah,  this solved the issue. Now I figured out what was going on. On
>> > adding echo $PATH at the beginning of the problematic function in
>> libtools
>> > script it was revealed that PATH  was set  to a different value.
>> >
>> > The key is in running 'make install' as 'sudo make install'. From man
>>
>> You shouldn't be using sudo.  You are installing into /tools as user lfs.
>>
>>    -- Bruce
>>
>> --
>> http://linuxfromscratch.org/mailman/listinfo/lfs-support
>> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
>> Unsubscribe: See the above information page
>>
>
>
> --
> http://linuxfromscratch.org/mailman/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
> Unsubscribe: See the above information page
>
>
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to