Where does the ELF binary dynamic library name come from?
Greetings,
These arguments (and others) are used with libtool:
-I/usr/local/include/guile/2.2 -L/usr/local/lib -lguile-2.2
yet readelf reveals:
# readelf -d /usr/local/bin/gschem | grep guile
0x0000000000000001 NEEDED Shared library: [libguile-2.0.so.22]
when it ought to point to:
libguile-2.2.so.1
Where does the ELF binary dynamic library name come from?
"Don" <[email protected]> writes:
Greetings,
These arguments (and others) are used with libtool:
-I/usr/local/include/guile/2.2 -L/usr/local/lib -lguile-2.2
yet readelf reveals:
# readelf -d /usr/local/bin/gschem | grep guile
0x0000000000000001 NEEDED Shared library: [libguile-2.0.so.22]
when it ought to point to:
libguile-2.2.so.1
Where does the ELF binary dynamic library name come from?
That's something which can only be guessed at with this level of
information. A possible scenario could be: Something linking with a
static version of libguile-2.2 also links with a dynamic libray linked
with libguile 2.0.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 741 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 63:26:09 |
| Calls: | 12,446 |
| Calls today: | 1 |
| Files: | 15,192 |
| Messages: | 6,537,529 |