Re: [OMPI devel] version number issues
On Sat, 2009-09-05 at 11:33 +0300, Jeff Squyres wrote: > On Sep 4, 2009, at 2:56 PM, Nadia Derbey wrote: > > > Actually, I didn't have the problem on my side, because hg is not > > known > > in my build environment. Never noticed these lines: > > > > - > > > > *** Checking versions > > checking for SVN version... ../configure: line 4285: hg: command not > > found > > done > > checking Open MPI version... 1.4a1hg > > > > > I changed the subject since we're digressing a bit off the original > RFC... > > This is an interesting failure mode that we evidently didn't consider > when we wrote that script. ;-) I guess we should check $? when > returning and ensure that the command executed properly. Agreed. > > The only question is -- should we abort in this case, or just put in > "unknown -- could not find hg" (or whatever) as the version? I would > lean towards the latter; +1 : I think asking people to have hg in their build environment is too constraining. Regards, Nadia > development machines may vary wildly in what > software is installed... Unless anyone objects, I'll do the latter. > -- Nadia Derbey
Re: [OMPI devel] libtool issue with crs/self
Hello,
* Josh Hursey wrote on Wed, Aug 05, 2009 at 04:51:59PM CEST:
> I noticed that the "-fvisibility=hidden" option when passed to
> libltdl will cause it to fail in its configure test for:
> "checking whether a program can dlopen itself"
> This is because the symbol they are trying to look for with dlsym()
> is not postfixed with:
> __attribute__ ((visibility("default")))
> If I do that, then the test passes correctly.
>
> I am not sure if this is a configure bug in Libtool or not.
I've brought this up on the Libtool list:
Thanks,
Ralf
Re: [OMPI devel] RFC - "system-wide-only" MCA parameters
- "Ralph Castain" wrote: > Let me point out the obvious since this has plagued > us at LANL with regard to this concept. If a user > wants to do something different, all they have to > do is download and build their own copy of OMPI. One possibility may be to have OMPI honour a config file in /etc by default as well as the ones in $prefix, so if a user built their own copy then they would have to hack the code in order to disable the check. I also really liked the idea of OMPI outputing a message if a user tried to override a locked param, much better to explain why something is bad rather than just saying "no" (especially if you can say "no, but you could try..."). cheers! Chris -- Christopher Samuel - (03) 9925 4751 - Systems Manager The Victorian Partnership for Advanced Computing P.O. Box 201, Carlton South, VIC 3053, Australia VPAC is a not-for-profit Registered Research Agency
