On Thu, 26 Nov 2020 10:45:58 +0900
Yotta Point <yottapo...@gmail.com> wrote:

> On Thu, Nov 26, 2020 at 10:40 AM Douglas R. Reno <
> ren...@linuxfromscratch.org> wrote:  
> 
> >
> > On 11/25/20 7:28 PM, Yotta Point wrote:
> >
> > Hi,
> >
> > I managed to build the LFS for 32Bit and now I am trying to make it
> > a 64Bit version.
> > I am stuck at step 5.5 Glibc build in the LSB compliance.
> >
> > case $(uname -m) in
> >     i?86)   ln -sfv ld-linux.so.2 $LFS/lib/ld-lsb.so.3
> >     ;;
> >     x86_64) ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64
> >             ln -sfv ../lib/ld-linux-x86-64.so.2
> > $LFS/lib64/ld-lsb-x86-64.so.3 ;;
> > esac
> >
> > the second ln is failing saying "No such file or directory" which
> > seems normal to me because the first line create a symlink at
> > $LFS/lib64 that links to a library, and the second line is trying
> > to access the symlink "$LFS/lib64" as if it was a directory. I am
> > missing something here ?
> >
> > Thanks for your help !
> >
> > Hi,
> >
> >
> > For 32-bit systems, only the line that starts with i?86 is
> > necessary. For 64-bit systems, you'd follow x86_64.
> >
> > Note that most users copy and paste that block of commands into
> > their terminal so the system follows what part is needed.
> >
> > - Doug
> > --
> > http://lists.linuxfromscratch.org/listinfo/lfs-support
> > FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> > Unsubscribe: See the above information page
> >
> > Do not top post on this list.
> >
> > A: Because it messes up the order in which people normally read
> > text. Q: Why is top-posting such a bad thing?
> > A: Top-posting.
> > Q: What is the most annoying thing in e-mail?
> >
> > http://en.wikipedia.org/wiki/Posting_style  
> 
> 
> Hey, thanks for your quick reply.
> Maybe I did not correctly explain my issue. In the x86_64) case,
> there are 2 commands.  "ln -sfv ../lib/ld-linux-x86-64.so.2
> $LFS/lib64" and " ln -sfv ../lib/ld-linux-x86-64.so.2
> $LFS/lib64/ld-lsb-x86-64.so.3". The second ln is giving me back "No
> such file or directory" and I think it's because the first "ln" is
> making "$LFS/lib64" a symlink to a library, and the second ln is
> trying to access "$LFS/lib64" as if it was a directory.
> 
> Sorry if my first post was not explicit enough.

Did a /lib64 directory in section 4.2?
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Reply via email to