[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
libelf.so/libnvpair.so build problem with MKUPDATE=yes
Since quite some time, i do notice some problems on my machines with
some libraries that are linked against themselves ... This currently
include `libelf.so.0.0' and `libnvpair.so.0.0'.
There is no problem when building the library for the first
time... But later, with MKUPDATE=yes, things goes badly generating the
Here follow the `libnvpair.so.0.0' case :
One of the source file `libnvpair.c' will generate a `libnvpair.so'
object for the dynamic library `libnvpair.so.0.0', and at that time a
symbolic link named `libnvpair.so' is made, which overwrite the
previously generated object file.
Next time the linker will be called to build the dynamic library, the
library itself will be added to the objects lists ... generating the
dependency loop i'm currently seeing.
njoly@lanfeust [lib/libnvpair]> objdump -x obj.amd64/libnvpair.so.0.0
obj.amd64/libnvpair.so.0.0: file format elf64-x86-64
architecture: i386:x86-64, flags 0x00000150:
HAS_SYMS, DYNAMIC, D_PAGED
start address 0x00000000000025c0
Any idea how to solve this, except by renaming the `libnvpair.c'
source file ?
Biological Software and Databanks.
Institut Pasteur, Paris.
Main Index |
Thread Index |