-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/07/11 19:18, Brice Goglin wrote:
> Christopher, it should work starting with trunk r3535.
Looks good to me with hwloc-1.3a1r3537. :-)
Thanks!
Chris
- --
Christopher Samuel - Senior Systems Administrator
VLSCI - Victorian Life Sciences Co
All this should be fixed now, and the configure output is now clear (it
doesn't change its mind about pci_init/cleanup or pci_lookup_name
without any obvious reason anymore).
FC7:
checking for pci/pci.h... yes
checking for pci_init in -lpci... no
checking for pci_init in -lpci with -lz... yes
chec
Le 29/06/2011 13:18, Brice Goglin a écrit :
> I don't think we finally fixed this.
>
> IIRC, we need either a way to bypass the cache, or always add -lresolv
> even if it's useless (or find another way to detect if lresolv is needed).
Redefining our own HWLOC_AC_CHECK_LIB_NO_CACHE looks possible.
I don't think we finally fixed this.
IIRC, we need either a way to bypass the cache, or always add -lresolv
even if it's useless (or find another way to detect if lresolv is needed).
Brice
pciutils was re-based to 3.1.7 in RHEL5.6 at the request of some of our
hardware partners, in order to add some new hardware support.
That'd explain why I didn't hit it when I was testing
previously, we were still on CentOS 5.4 and RHEL 5.5
then so obviously this dependency is new in RHEL 5.
On Jun 17, 2011, at 7:52 AM, Brice Goglin wrote:
> Advice from colleagues: This is becoming too ugly, this is libpci's
> fault, just always add -lz -lresolv and let the linker drop them later
> if they're useless :)
Then we (might/probably will) get linker warnings when building hwloc.
I'll tink
On Jun 17, 2011, at 4:04 AM, Christopher Samuel wrote:
>> Is there anyway to tell autoconf to ignore/drop some cached results?
>> Resetting the value of ac_cv_lib_pci_pci_lookup_name may work but I
>> don't know if we can do that (if we can, we should do it for
>> pci_init/pci_cleanup vs -lz too).
Advice from colleagues: This is becoming too ugly, this is libpci's
fault, just always add -lz -lresolv and let the linker drop them later
if they're useless :)
Brice
Le 17/06/2011 10:04, Christopher Samuel a écrit :
> On 17/06/11 17:14, Brice Goglin wrote:
>
> > Is there anyway to tell autoconf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/06/11 17:14, Brice Goglin wrote:
> Is there anyway to tell autoconf to ignore/drop some cached results?
> Resetting the value of ac_cv_lib_pci_pci_lookup_name may work but I
> don't know if we can do that (if we can, we should do it for
> pci_in
Le 17/06/2011 08:40, Christopher Samuel a écrit :
> On 17/06/11 05:32, Jeff Squyres wrote:
>
> > Ok, good. I'll see if I can code this up.
>
> > ...done. Try a nightly trunk tarball >=r3516
> > (new nightly should be made in about 6 hours).
>
> Hmm, now it looks like it doesn't correctly enable
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/06/11 05:32, Jeff Squyres wrote:
> Ok, good. I'll see if I can code this up.
>
> ...done. Try a nightly trunk tarball >=r3516
> (new nightly should be made in about 6 hours).
Hmm, now it looks like it doesn't correctly enable
pci support..
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/06/11 05:32, Jeff Squyres wrote:
> Ok, good. I'll see if I can code this up.
>
> ...done. Try a nightly trunk tarball >=r3516 (new nightly should be made in
> about 6 hours).
Thanks, will give it a go..
> [11:47] svbu-mpi:~ % cat /etc/issu
On Jun 14, 2011, at 8:06 PM, Christopher Samuel wrote:
>> Chris -- can you try linking this simple app to see if
>> it causes the linker error, and further try adding
>> -lresolv to see if that fixes the error?
>
> Yup - that does it and the error confirms the symbol
> that is causing this odd be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/06/11 22:39, Jeff Squyres wrote:
> Chris -- can you try linking this simple app to see if
> it causes the linker error, and further try adding
> -lresolv to see if that fixes the error?
Yup - that does it and the error confirms the symbol
that
On Jun 13, 2011, at 8:30 PM, Christopher Samuel wrote:
> Well oddly only one of the 2 locations had been built
> (the one with the makelog), but just in case I've redone
> it from scratch - compressed and attached.
Ok, these seem consistent. Thanks!
It looks like our test might not be hitting t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/06/11 10:08, Christopher Samuel wrote:
> I'll fix that up and send it on again..
Well oddly only one of the 2 locations had been built
(the one with the makelog), but just in case I've redone
it from scratch - compressed and attached.
cheers,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/06/11 00:17, Jeff Squyres wrote:
> Heh; next time you might want to compress. :-)
Er, I think I forgot - it was late here.. ;-)
> I got the logs; I'm looking at them now...
Cool.
> Are you sure that the config.log you sent matches
> the mak
Le 13/06/2011 22:38, Samuel Thibault a écrit :
> Hello,
>
> Christopher Samuel, le Sun 12 Jun 2011 07:45:48 +0200, a écrit :
>>> I fail to see how that symbol can ever get into
>>> libhwloc.so, as we don't do any network thing at all...
>> I *suspect* it's being pulled in by libpci - here:
>>
>> $
Hello,
Christopher Samuel, le Sun 12 Jun 2011 07:45:48 +0200, a écrit :
> > I fail to see how that symbol can ever get into
> > libhwloc.so, as we don't do any network thing at all...
>
> I *suspect* it's being pulled in by libpci - here:
>
> $ nm /usr/lib/libpci.a | grep res_query
> U
Heh; next time you might want to compress. :-)
I got the logs; I'm looking at them now...
Are you sure that the config.log you sent matches the makelog.txt? I see PCI
checks in the configure stdout, but nothing about that in config.log...
On Jun 13, 2011, at 9:28 AM, Christopher Samuel wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/06/11 23:11, Jeff Squyres wrote:
> Chris -- could you send your config.log?
Posted but currently held for moderation due to size..
- --
Christopher Samuel - Senior Systems Administrator
VLSCI - Victorian Life Sciences Computation Initiat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/06/11 23:11, Jeff Squyres wrote:
> Chris -- could you send your config.log?
Sure - attached to this email, along with a "makelog"
which contains the output of configure && make V=1.
> I'd like to see how it's deciding that libpci is ok
> in c
On Jun 13, 2011, at 9:01 AM, Brice Goglin wrote:
> If you pass PCI_LOOKUP_NETWORK to the name-lookup functions (we don't),
> pci_id_net_lookup() gets called and it does a DNS-like resolving. No idea how
> it works.
But I think that if we're linking against libpci.a, it's going to need to
resol
Le 13/06/2011 14:45, Jeff Squyres a écrit :
> Ah, that might explain it, then.
>
> I guess this means we need to add a few configure tests to figure out
the dependencies of libpci (if any). Yuck.
>
> Do we have any idea what function in libpci is calling the resolver
functionality?
If you pass PCI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/06/11 22:45, Jeff Squyres wrote:
> Ah, that might explain it, then.
Yeah.. :-(
> I guess this means we need to add a few configure tests
> to figure out the dependencies of libpci (if any). Yuck.
Indeed.
> Do we have any idea what function
Ah, that might explain it, then.
I guess this means we need to add a few configure tests to figure out the
dependencies of libpci (if any). Yuck.
Do we have any idea what function in libpci is calling the resolver
functionality?
On Jun 13, 2011, at 8:42 AM, Christopher Samuel wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/06/11 22:22, Jeff Squyres wrote:
> Chris -- does nm on your libpci not show this?
Nope, there is no libpci.so* on RHEL5.6, just a libpci.a.
(and no, I've no idea why either!)
cheers!
Chris
- --
Christopher Samuel - Senior Systems Adminis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/06/11 19:41, Brice Goglin wrote:
> 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?
Yup, configure works just
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@savbu-ssd-linux ~]# ldd /lib64/libpci.so.3
linux-vdso.so.1 => (0x7fffcc7ff000)
libresolv.so.2 => /lib64/libresolv.so.2
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. Howe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
OK, looks like libpci may well be the culprit. Linking
with the default libtool c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/06/11 11:42, Christopher Samuel wrote:
> CCLD lstopo
> /tmp/hwloc-1.3a1r3511/src/.libs/libhwloc.so: undefined reference to
> `__res_query'
For the record this happens with system GCC & GCC 4.4,
Intel compilers and PGI compilers on RHEL 5.6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/06/11 11:55, Samuel Thibault wrote:
> Could you look for this in your /usr/include?
$ grep -R __res_query /usr/include/
/usr/include/resolv.h:#define res_query __res_query
/usr/include/resolv.h:#define res_querydomain __res_qu
Christopher Samuel, le Sun 12 Jun 2011 03:43:08 +0200, a écrit :
> CCLD lstopo
> /tmp/hwloc-1.3a1r3511/src/.libs/libhwloc.so: undefined reference to
> `__res_query'
Could you look for this in your /usr/include?
I fail to see how that symbol can ever get into libhwloc.so, as we don't
do any n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
Just had a quick play with 1.3a1r3511 and found that whilst
it builds happily on Ubuntu 11.04 it fails to compile (link)
on CentOS 5.6 & RHEL 5.6 with:
CCLD lstopo
/tmp/hwloc-1.3a1r3511/src/.libs/libhwloc.so: undefined reference to
`__
35 matches
Mail list logo
