This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
Shouldn't the linker be pulling in these dependent libraries automatically if libpci was built properly?
E.g., when I look on my RHEL6 system, I see:
[root_at_savbu-ssd-linux ~]# ldd /lib64/libpci.so.3
linux-vdso.so.1 => (0x00007fffcc7ff000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x0000003911c00000)
libc.so.6 => /lib64/libc.so.6 (0x0000003910000000)
Which means that the linker will pull in libresolv at run if it wants/needs to, without needing to specify -lresolv on the command line.
Chris -- does nm on your libpci not show this?
On Jun 13, 2011, at 5:41 AM, Brice Goglin wrote:
> Le 13/06/2011 11:11, Christopher Samuel a écrit :
>> On 12/06/11 15:45, Christopher Samuel wrote:
>>> I *suspect* it's being pulled in by libpci - here:
>>> $ nm /usr/lib/libpci.a | grep res_query
>>> U __res_query
> Hello Chris,
> libpci needs -lz in some cases, maybe it needs more. However, in the
> case of -lz, we failed to configure if we didn't add -lz to
> AC_CHECK_LIB. Your configure works fine, right?
> hwloc-devel mailing list
For corporate legal information go to: