On 2016-07-18 18:04, William Harrington wrote:
> On Mon, July 18, 2016 13:02, Maxwell Dreytser wrote: > > /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.0/../../../../lib64/libcrypto.a(dso_dlfcn.o): > In function `dlfcn_globallookup': > dso_dlfcn.c:(.text+0x11): undefined reference to `dlopen' > dso_dlfcn.c:(.text+0x24): undefined reference to `dlsym' > dso_dlfcn.c:(.text+0x2f): undefined reference to `dlclose' ... > root:/lib#$ find / -name "libdl*" > /lib/libdl.so.2 > /lib/libdl-2.23.so > /tools/lib/libdl.a > /tools/lib/libdl.so.2 > /tools/lib/libdl.so > /tools/lib/libdl-2.23.so > /usr/lib/libdl.a > /usr/lib/libdl.so > > As you can see, its there. > > Maxwell. Hello Maxwell, Since you have libcrypto in /usr/lib64 and libdl was only found in /lib and /usr/lib, then I'm suspecting you have separate lib, /usr/lib, lib64 and /usr/lib64 directories not linked. This is something you may wish to verify. In the current book, ch5 binutils creates the proper /tools/lib and /tools/lib64. For chapter 6, it is during the directories creation process. Sincerely, William Harrington Hello William, `/lib64' seems to be a symlink to `/lib', same for /usr/lib64: root:/#$ ls -l /lib64 lrwxrwxrwx 1 root root 3 Jul 17 03:54 /lib64 -> lib root:/#$ ls -l /usr/lib64 lrwxrwxrwx 1 root root 3 Jul 17 03:54 /usr/lib64 -> lib Maxwell.
-- 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
