On 11/25/20 7:45 PM, Yotta Point wrote:
On Thu, Nov 26, 2020 at 10:40 AM Douglas R. Reno
<ren...@linuxfromscratch.org <mailto: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.
Hi,
No worries on explicitness, I might be misunderstanding the question as
well. I'm going off of the fact that you said that you're building
32-bit LFS (which is something Thomas and I primarily do).
If you're building a 32-bit system, you should most certainly ignore the
block for x86_64. /lib64 is for $LFS/lib64 is for a couple of symbolic
links to libraries used to provide compatibility with existing 64-bit
binaries on 64-bit systems. On a 32-bit system, you shouldn't have
$LFS/lib64 :-) you can ignore the block for x86_64.
To revert that (you don't want 64-bit libraries on a 32-bit system),
run: "rm -fv $LFS/lib64".
- 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
