<div dir="ltr"><div>Just noticed another INPUT statement also refers to dl as:<br><br><div style="margin-left:40px">/usr/local/lib/fpc/2.7.1/units/arm-linux/rtl/dl.o<br></div><br></div>This appears ahead of the -ldl statement.<br>
<br>Could this be the problem? -b<br><div><br><div><br><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 23, 2013 at 10:32 PM, Bruce Tulloch <span dir="ltr"><<a href="mailto:pascal@causal.com" target="_blank">pascal@causal.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Yes, it's in the search path as:<br><div><br><div style="margin-left:40px">root@beria:/lib/arm-linux-gnueabihf# ls -l libdl*<br>
-rw-r--r-- 1 root root 9812 Feb 23 00:37 <a href="http://libdl-2.13.so" target="_blank">libdl-2.13.so</a><br>
lrwxrwxrwx 1 root root 13 Feb 23 00:37 libdl.so.2 -> <a href="http://libdl-2.13.so" target="_blank">libdl-2.13.so</a><br></div><br></div><div>It's referred to in an INPUT statement in link.res as:<br><br><div style="margin-left:40px">
INPUT(<br>-lpthread<br>-ldl<br>)<br></div><br></div><div>and there are two search statements:<br><br><div style="margin-left:40px">SEARCH_DIR("/usr/local/opt/chroot/raspbian/rootfs/usr/lib/arm-linux-gnueabihf/")<br>
SEARCH_DIR("/usr/local/opt/chroot/raspbian/rootfs/lib/arm-linux-gnueabihf/")<br></div><br></div><div>at the top of the file which suggest it should be found okay.<br></div><div><br></div></div><div class="HOEnZb">
<div class="h5"><div class="gmail_extra">
<br><br><div class="gmail_quote">On Thu, May 23, 2013 at 10:28 PM, Jonas Maebe <span dir="ltr"><<a href="mailto:jonas.maebe@elis.ugent.be" target="_blank">jonas.maebe@elis.ugent.be</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
On 23 May 2013, at 14:25, Bruce Tulloch wrote:<br>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
On Thu, May 23, 2013 at 10:18 PM, Jonas Maebe <<a href="mailto:jonas.maebe@elis.ugent.be" target="_blank">jonas.maebe@elis.ugent.be</a>><u></u>wrote:<br>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
On 23 May 2013, at 14:10, Bruce Tulloch wrote:<br>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Linking arm-test-threads<br>
/usr/local/lib/fpc/2.7.1/<br>
units/arm-linux/rtl/cthreads.*<u></u>*o: In function<br>
`CTHREADS_$$_LOADPTHREADS$$**<u></u>BOOLEAN':<br>
cthreads.pp:(.text.n_cthreads_<u></u>**$$_loadpthreads$$boolean+<u></u>0xc): warning:<div><br>
Using<br>
'dlopen' in statically linked applications requires at runtime the shared<br>
libraries from the glibc version used for linking<br>
<br>
</div></blockquote><div>
<br>
Why/how are you trying to create a statically linked binary? As the<br>
message above explains, statically linking libdl relies on a bunch of<br>
library magic. At the very least you'll probably also have to link libc<br>
explicitly, but I would really recommend to link dynamically instead.<br>
Support for binaries statically linked against C libraries is generally<br>
very much untested, and known not to work on certain platforms (e.g.<br>
Linux/x86-64).<br>
<br>
</div></blockquote><div>
Okay, so I'm not trying to link statically, not intentionally anyway.<br>
</div></blockquote>
<br>
Do you have a libdl.so in your library search path? And what kind of reference to libdl does link.res contain?<div><div><br>
<br>
<br>
Jonas<br>
______________________________<u></u>_________________<br>
fpc-pascal maillist - <a href="mailto:fpc-pascal@lists.freepascal.org" target="_blank">fpc-pascal@lists.freepascal.<u></u>org</a><br>
<a href="http://lists.freepascal.org/mailman/listinfo/fpc-pascal" target="_blank">http://lists.freepascal.org/<u></u>mailman/listinfo/fpc-pascal</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>