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
peo
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
> Enrique L
Enrique Larraia wrote:
> 2014/1/22 Pierre M.R.
>
>> 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
On Wed, Jan 22, 2014 at 10:11:29PM +, akhiezer wrote:
>
>
> (( p.s. Although - and excuse the/any noise - OTTOMH am not sure why sudo
> need be part of the picture if the 'su - lfs' is done in '4.3. Adding the
> LFS User'. Also noticed earlier that the 'problematic' ranlib in your
> /tools
> Date: Wed, 22 Jan 2014 21:50:02 +
> From: lf...@cruziero.com (akhiezer)
> To: LFS Support List
> Subject: Re: [lfs-support] 5.8 Libstdc++-4.8.1
>
> > Date: Fri, 17 Jan 2014 22:17:42 -0600
> > From: Louis Rine
> > To: LFS Support List
> > Subject
> Date: Fri, 17 Jan 2014 22:17:42 -0600
> From: Louis Rine
> To: LFS Support List
> Subject: Re: [lfs-support] 5.8 Libstdc++-4.8.1
>
Louis,
In case you've not already seen it: there may be a solution to the issue
you're seeing:
Enrique Larraia
Wed Jan 22 21:4
2014/1/22 Pierre M.R.
> 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 li
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
Pierre
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Hi,
Thanks for the replies. First, yes, I removed directories gcc-4.8.1 and
gcc-build before start building libstdc++-4.8.1, so this shouldn't be a
problem... The 686-lfs-linux-gnu-ranlib file is there (together with many
others) and is executable
lfs@tornasol:/mnt/lfs/tools/bin$ ls -l i686-lfs-l
On Wed, Jan 22, 2014 at 11:40:44AM +0100, Pierre M.R. wrote:
> Enrique Larraia wrote:
> > libtool: install: i686-lfs-linux-gnu-ranlib /tools/lib/libsupc++.a
> > ../libtool: line 1132: i686-lfs-linux-gnu-ranlib: command not found
> The error message comes from bash. It looks like 'make install' rese
Enrique Larraia wrote:
> libtool: install: i686-lfs-linux-gnu-ranlib /tools/lib/libsupc++.a
> ../libtool: line 1132: i686-lfs-linux-gnu-ranlib: command not found
The error message comes from bash. It looks like 'make install' reset
the shell PATH. I would suspect some security magics like selinux.
Ken Moffat wrote:
> On Wed, Jan 22, 2014 at 12:23:26AM +, Ken Moffat wrote:
>> On Tue, Jan 21, 2014 at 09:53:03PM +, Enrique Larraia wrote:
>>
>> Your error was
>>> libtool: install: chmod 644 /tools/lib/libsupc++.a
>>> libtool: install: i686-lfs-linux-gnu-ranlib /tools/lib/libsupc++.a
>>
On Wed, Jan 22, 2014 at 12:23:26AM +, Ken Moffat wrote:
> On Tue, Jan 21, 2014 at 09:53:03PM +, Enrique Larraia wrote:
>
> Your error was
> > libtool: install: chmod 644 /tools/lib/libsupc++.a
> > libtool: install: i686-lfs-linux-gnu-ranlib /tools/lib/libsupc++.a
> > ../libtool: line 1132
On Tue, Jan 21, 2014 at 09:53:03PM +, Enrique Larraia wrote:
> Hi all,
>
> I'm experiencing the same issue as Louis Rine in this thread:
>
> https://www.mail-archive.com/lfs-support@linuxfromscratch.org/msg21373.html
>
> I'm unsure whether or not reply to the cited thread, or create one on m
Hi all,
I'm experiencing the same issue as Louis Rine in this thread:
https://www.mail-archive.com/lfs-support@linuxfromscratch.org/msg21373.html
I'm unsure whether or not reply to the cited thread, or create one on my
own. I apologize if this causes a duplication of the same topic :(
I got the
On Sat, Jan 18, 2014 at 01:28:58PM +, akhiezer wrote:
> > Date: Fri, 17 Jan 2014 22:17:42 -0600
> > From: Louis Rine
> > To: LFS Support List
> > Subject: Re: [lfs-support] 5.8 Libstdc++-4.8.1
> >
> .
> .
> >
> > Anyway, as for t
On Jan 17, 2014, at 12:43 PM, Douglas R. Reno wrote:
> I do not believe that the LFS Livecd works on any version over 7.0
>
> Source: LFS LiveCD project homepage
>
> Douglas Reno
>
If you want to use an updated lfs livecd for currenet LFS versions,
then use this one. I do not upgrade it, anymor
Le 17/01/2014 19:37, Louis Rine a écrit :
> I ran the build again after fixing /bin/sh to be a link to /bin/bash. I
> formatted the lfs partition and re-downloaded the sources before running the
> build again, but it occurred to me after the fact that I didn't delete the lfs
> programs from /tools/
> Date: Fri, 17 Jan 2014 22:17:42 -0600
> From: Louis Rine
> To: LFS Support List
> Subject: Re: [lfs-support] 5.8 Libstdc++-4.8.1
>
.
.
>
> Anyway, as for those sanity checks:
>
> $ ls -laF /tools/bin/x86_64-lfs-linux-gnu-ranlib
> -rwxr-xr-x 2
> Date: Thu, 16 Jan 2014 17:47:42 -0600
> From: Louis Rine
> To: LFS Support List
> Subject: Re: [lfs-support] 5.8 Libstdc++-4.8.1
>
> If this is the correct use of ldd...
>
> :~$ ldd /tools/bin/x86_64-lfs-linux-gnu-ranlib
> linux-vdso.so.1 => (0x7ff
; > To: LFS Support List
> > Subject: Re: [lfs-support] 5.8 Libstdc++-4.8.1
> >
> >
> > I ran the build again after fixing /bin/sh to be a link to /bin/bash. I
> > formatted the lfs partition and re-downloaded the sources before running
> > the build again, but it
> Date: Fri, 17 Jan 2014 12:37:16 -0600
> From: Louis Rine
> To: LFS Support List
> Subject: Re: [lfs-support] 5.8 Libstdc++-4.8.1
>
>
> I ran the build again after fixing /bin/sh to be a link to /bin/bash. I
> formatted the lfs partition and re-downloaded the sources be
Oh, darn. I ought to have looked at that. Thank you for pointing that out.
:) Hmm.
On Fri, Jan 17, 2014 at 12:43 PM, Douglas R. Reno wrote:
> I do not believe that the LFS Livecd works on any version over 7.0
>
> Source: LFS LiveCD project homepage
>
> Douglas Reno
>
> --
> http://linuxfromscrat
I do not believe that the LFS Livecd works on any version over 7.0
Source: LFS LiveCD project homepage
Douglas Reno
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
I ran the build again after fixing /bin/sh to be a link to /bin/bash. I
formatted the lfs partition and re-downloaded the sources before running
the build again, but it occurred to me after the fact that I didn't delete
the lfs programs from /tools/bin. So maybe that was dumb.
I did get the same e
On Jan 16, 2014, at 5:56 PM, Louis Rine wrote:
> Ah, I was wondering if dash would make a difference. I will fix that
> and try again. Thank you. :)
It does, and that is why the host system requirements states:
Bash-3.2 (/bin/sh should be a symbolic or hard link to bash)
But that may not be
Ah, I was wondering if dash would make a difference. I will fix that and
try again. Thank you. :)
On Thu, Jan 16, 2014 at 5:53 PM, Ken Moffat wrote:
> On Thu, Jan 16, 2014 at 05:47:42PM -0600, Louis Rine wrote:
> > If this is the correct use of ldd...
> >
> > :~$ ldd /tools/bin/x86_64-lfs-linux
On Thu, Jan 16, 2014 at 05:47:42PM -0600, Louis Rine wrote:
> If this is the correct use of ldd...
>
> :~$ ldd /tools/bin/x86_64-lfs-linux-gnu-ranlib
> linux-vdso.so.1 => (0x7fffa837b000)
> libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7ff874f03000)
> libc.so.6 =
If this is the correct use of ldd...
:~$ ldd /tools/bin/x86_64-lfs-linux-gnu-ranlib
linux-vdso.so.1 => (0x7fffa837b000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7ff874f03000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7ff874b3a000)
/lib64/ld
On Thu, Jan 16, 2014 at 04:23:51PM -0600, Louis Rine wrote:
> Hello all. :)
>
> I'v gone through the book a couple times in the past on i686, but this is
> my first time around with x86_64. All seemed to go well until I ran into
> this little gem while installing libstdc++:
>
> <...lots of compil
Hello all. :)
I'v gone through the book a couple times in the past on i686, but this is
my first time around with x86_64. All seemed to go well until I ran into
this little gem while installing libstdc++:
<...lots of compilation output...>
Making install in libsupc++
make[1]: Entering directory `
31 matches
Mail list logo
