| 1 |
Hi Antoine, |
| 2 |
|
| 3 |
Antoine Dechaume <boolegue@×××××.com> writes: |
| 4 |
|
| 5 |
> this is the error I get inside gentoo-rap when running an executable |
| 6 |
> and libraries build on another platform: |
| 7 |
> lect: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by |
| 8 |
> /XXX/gentoo-rap/usr/lib64/libcgns.so) |
| 9 |
> lect: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by |
| 10 |
> /XXX/gentoo-rap/usr/lib64/libpython2.7.so.1.0) |
| 11 |
|
| 12 |
The binary is interpretated by the host /lib64/ld-linux-x86-64.so.2 but |
| 13 |
it somehow loads python runtime from RAP (which is compiled with a newer |
| 14 |
version of glibc). The old /lib64/ld-linux-x86-64.so.2 cannot resolve that. |
| 15 |
|
| 16 |
3 possible solutions: |
| 17 |
|
| 18 |
1. find out how the binary loaded libpython, and point it to the host |
| 19 |
libpython instead. |
| 20 |
|
| 21 |
2. execute the binary by RAP dynamic linker explicitly: |
| 22 |
|
| 23 |
/XXX/gentoo-rap/lib64/ld-linux-x86-64.so.2 <binary> |
| 24 |
|
| 25 |
you can use patchelf to rewrite the program interpreter. |
| 26 |
|
| 27 |
3. rebuild the binary with Gentoo RAP gcc. |
| 28 |
|
| 29 |
Yours, |
| 30 |
Benda |
| 31 |
|
| 32 |
Reference: https://greek0.net/elf.html |
| 33 |
section "Dynamic linking and the ELF interpreter" |
Archives