Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.1a1r2166
Start time: Fri May 28 21:01:05 EDT 2010
End time: Fri May 28 21:03:03 EDT 2010
Your friendly daemon,
Cyrador
bgog...@osl.iu.edu, le Fri 28 May 2010 11:27:47 -0400, a écrit :
> Add a backend info string, except in XML since we may not want to override
> the one that we got from the XML file
>
> + add_object_info(topology->levels[0][0], strdup("Backend=AIX"));
Mmm, this will probably need to be extendab
Posted:
http://www.open-mpi.org/software/hwloc/v1.0/
(I was assuming we'd need at least an rc2, so I went ahead and did this before
bringing over the NEWS bullets)
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/
Le 28/05/2010 17:17, Jeff Squyres a écrit :
Please look over the points I just drafted for v1.0.1; add / edit / delete as
necessary.
Looks good.
I like citing users who have been helpful in the NEWS file; it's a (small) way of
saying "thank you!".
Me too.
Brice
Please look over the points I just drafted for v1.0.1; add / edit / delete as
necessary. I like citing users who have been helpful in the NEWS file; it's a
(small) way of saying "thank you!".
When we're done, we can copy the finished points to the v1.0 branch NEWS file.
Thanks!
Begin forwar
Jeff Squyres, le Fri 28 May 2010 09:03:30 -0400, a écrit :
> On May 28, 2010, at 9:01 AM, Samuel Thibault wrote:
>
> > > ...actually, I'm not seeing where we use epstopdf in our build process...?
> >
> > I believe it's hidden somewhere in pdflatex or such call.
>
> Is it our responsibility to ch
On May 28, 2010, at 9:01 AM, Samuel Thibault wrote:
> > ...actually, I'm not seeing where we use epstopdf in our build process...?
>
> I believe it's hidden somewhere in pdflatex or such call.
Is it our responsibility to check for it, then?
--
Jeff Squyres
jsquy...@cisco.com
For corporate lega
Jeff Squyres, le Fri 28 May 2010 08:54:33 -0400, a écrit :
> On May 28, 2010, at 7:27 AM, Brice Goglin wrote:
>
> > I am not sure where/how to do #1 so I'll be happy if you do it :)
>
> ...actually, I'm not seeing where we use epstopdf in our build process...?
I believe it's hidden somewhere in
On May 28, 2010, at 7:27 AM, Brice Goglin wrote:
> I am not sure where/how to do #1 so I'll be happy if you do it :)
...actually, I'm not seeing where we use epstopdf in our build process...?
Is it invoked indirectly by some other tool? It doesn't seem to be invoked at
all on my Mac.
--
Jeff
I am not sure where/how to do #1 so I'll be happy if you do it :)
Brice
Le 28/05/2010 12:24, Jeff Squyres (jsquyres) a écrit :
Both sound fine to me.
Do you want to do #1 or do you want me to do it?
-jms
Sent from my PDA. No type good.
- Original Message -
From: hwloc-devel-boun.
Good call; thanks for the reminder. Thankfully, hwloc doesn't suffer from such
issues (I just sanity checked the trunk and v1.0 to be sure).
IIRC, the main issues in OMPI surrounded the use of its wrapper compilers
(i.e., trying to exec something with "gcc -m32" wouldn't work -- you have to
Anything else we want to put into 1.0.1? Or should I make an rc?
There were a few minor changes (I'm afk and can't check the svn log atm) but I
think the 2 big ones were the windows fix and the 32 bit fix.
-jms
Sent from my PDA. No type good.
Hi,
sorry to chime in so late. Jeff you may remember that I reported a
similar problem to open-mpi some years ago. But I didn't use
CFLAGS=-m32 but CC="gcc -m32" and CXX="g++ -m32", which is still in my
eyes the correct way to pass this flag to all compile commands. The
problem in open-mpi back th
Both sound fine to me.
Do you want to do #1 or do you want me to do it?
-jms
Sent from my PDA. No type good.
- Original Message -
From: hwloc-devel-boun...@open-mpi.org
To: hwloc-de...@openmpi.org
Sent: Fri May 28 01:05:04 2010
Subject: [hwloc-devel] misc questions
A couple random q
A couple random questions:
* After installing my new laptop, it took me quite some time to figure
out that building hwloc from SVN failed because epstopdf was missing.
Could we check for it at configure or build time ? (we already check for
things like fig2dev)
* Updating the test topology outp
15 matches
Mail list logo
