On 10/21/2009 10:38 AM, Samuel Thibault wrote:
> Pavan Balaji, le Wed 21 Oct 2009 10:36:33 -0500, a écrit :
>> On 10/21/2009 10:28 AM, Samuel Thibault wrote:
>>> Pavan Balaji, le Wed 21 Oct 2009 09:55:36 -0500, a écrit :
1. I see a AC_PROG_CC_C99 in the configure.ac. Do you require the
On Oct 21, 2009, at 10:26 AM, Samuel Thibault wrote:
> What I meant is that *our* ibverbs.h code is Linux specific (it
uses a
> sysfs specific nice feature of OFED/Linux).
Can't we just make it a real function and not an inline? As it is now
it will not include the linux version in
On Oct 21, 2009, at 10:20 AM, Samuel Thibault wrote:
I've checked configure, only the check for egrep may fail and does not
provide any fallback which we could have used. It's only used for the
documentation generation, Jeff, maybe we can find an alternative to
egrep for what we use it for?
FWIW, I see at least some GNU-isms in the hwloc code that might be
problematic for embedding hwloc in other code bases that don't use gcc
to compile. E.g., in OMPI, we'd prefer to use the same compiler suite
to compile hwloc that was used to compile OMPI itself (e.g., intel,
PGI, ...etc.
Pavan --
Can you send a copy of your stderr? I don't get the warnings about
fgets output not getting checked.
Thanks!
On Oct 21, 2009, at 9:39 AM, hwloc wrote:
#16: hwloc build fails with strict compiler flags
---
Jeff Squyres, le Wed 21 Oct 2009 12:46:38 -0400, a écrit :
> I'd be surprised if there's a system out there that doesn't have some
> flavor of egrep that satisfies AC_PROG_EGREP (especially if Libtool
> uses it heavily). Do we know if this is the case, or is this a
> hypothetical that a
Jeff Squyres, le Wed 21 Oct 2009 12:50:55 -0400, a écrit :
> configuring/building hwloc with icc results in a *lot*
> of warnings; I didn't test functionality).
Mmm, I have already successfully tested with icc9.
The kind of warnings I've seen were not worth fixing to my mind: unused
> Pavan -- is it a problem to always compile hwloc with gcc?
Yeah, this will be a problem. For us to enable hwloc by default, it'll
need to build with all compilers and on all platforms without errors
(and hopefully without warnings either).
-- Pavan
--
Pavan Balaji
On 10/21/2009 11:59 AM, Jeff Squyres wrote:
> Can you send a copy of your stderr? I don't get the warnings about
> fgets output not getting checked.
Here you go:
libtool: compile: gcc -DHAVE_CONFIG_H -I.
-I/home/balaji/projects/mpich2/hydra/hydra/tools/bind/hwloc/hwloc/src
On Oct 21, 2009, at 1:18 PM, Samuel Thibault wrote:
> configuring/building hwloc with icc results in a *lot*
> of warnings; I didn't test functionality).
Mmm, I have already successfully tested with icc9.
The kind of warnings I've seen were not worth fixing to my mind:
unused
parameters,
The IU sysadmins fixed something with trac today such that we should
now get mails for trac ticket actions (to the hwloc-bugs list).
Also, FWIW, I also follow the Trac RSS feed, which shows commits,
ticket actions, and wiki changes (customize the URL parameters to your
liking):
Cool; I filed #18 and #19 about these. I'll fix the "mixed
declarations and code" issue right now.
On Oct 21, 2009, at 1:45 PM, Pavan Balaji wrote:
On 10/21/2009 11:59 AM, Jeff Squyres wrote:
> Can you send a copy of your stderr? I don't get the warnings about
> fgets output not getting
On 10/21/2009 10:38 AM, Samuel Thibault wrote:
> Pavan Balaji, le Wed 21 Oct 2009 10:36:33 -0500, a écrit :
>> On 10/21/2009 10:28 AM, Samuel Thibault wrote:
>>> Pavan Balaji, le Wed 21 Oct 2009 09:55:36 -0500, a écrit :
1. I see a AC_PROG_CC_C99 in the configure.ac. Do you require the
On Oct 20, 2009, at 8:33 PM, Jeff Squyres wrote:
Brice -- do you need to move r1195 and r1196 to the v0.9 branch?
I effectively just brought these over to the v0.9 branch.
With all these changes, I'll cut an rc2 and post it shortly.
--
Jeff Squyres
jsquy...@cisco.com
Jeff Squyres wrote:
> On Oct 20, 2009, at 8:33 PM, Jeff Squyres wrote:
>
>> Brice -- do you need to move r1195 and r1196 to the v0.9 branch?
>
> I effectively just brought these over to the v0.9 branch.
>
> With all these changes, I'll cut an rc2 and post it shortly.
Am I still supposed to make
Now that I try to implement it, I remember why an inline is convenient:
it doesn't require any build-time/run-time dependency unless you really
use it. If we make this code non-inline, we actually need libibverbs at
build time and runtime. Distro packages will have to depend on
libibverbs, and
On 10/21/2009 04:44 PM, Samuel Thibault wrote:
> Pavan Balaji, le Wed 21 Oct 2009 16:40:42 -0500, a écrit :
>>> Please read this thread:
>>>
>>> http://www.open-mpi.org/community/lists/hwloc-devel/2009/09/0054.php
>> Thanks. Is the only issue to not use AC_C_RESTRICT that of conflicting
>> name
Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.0a1r1216
Start time: Wed Oct 21 21:01:01 EDT 2009
End time: Wed Oct 21 21:03:07 EDT 2009
Your friendly daemon,
Cyrador
Tried building 0.9.1rc2 with gcc, icc, suncc and pgcc. Builds fine with
gcc. Lots of warnings with icc (as Jeff pointed out). Does not build
with suncc and pgcc.
With suncc (sunstudio 12):
==
source='topology-linux.c'
19 matches
Mail list logo
