'tis already in the README.
Someday we'll have nice glossy PDF's like LAM, but for the beta, the
README is what you get. :-)
On Jun 17, 2005, at 1:11 PM, Ben Allan wrote:
Please paste the quoted text (appropriately expanded)
into a readme or install or some other prominent doc location/app
Please paste the quoted text (appropriately expanded)
into a readme or install or some other prominent doc location/appendix
as soon as possible if it isn't there already.
Details like this matter a lot to a few of us,
and many of us haven't drunk completely the 3000 gallons of twisted logic
that
On Jun 16, 2005, at 7:10 PM, Ben Allan wrote:
The *only* flag that mpicc (and friends) recognizes is --showme.
*Everything* else is passed to the underlying compiler. We didn't
want
to take the chance, for example, that --help was actually a valid flag
for the underlying compiler.
So is thi
On Thu, Jun 16, 2005 at 06:33:51PM -0400, Jeff Squyres wrote:
> On Jun 16, 2005, at 2:58 PM, Ben Allan wrote:
>
> The only reason to have something like ompiConf.sh is to use the
> frameworks that already exist (like the gnome-conf thingy). I was only
> tossing that out as an example -- I didn'
On Jun 16, 2005, at 2:58 PM, Ben Allan wrote:
Ah -- I thought that that would be a different issue (I presume you're
speaking of the compile/lib flags command, like gnome-config et
al.)...? Are you saying that the compile/lib flags should be
accessible from ompi_info in a fine-grained fashion a
Ben Allan writes:
> I tried that just now and it doesn't look different. Will check your
> other mail (which apparently i haven't reached yet in the mail reader).
> I take that back, apparently -parseable isn't recognized but -parsable
> is. A :-separated output results. tolerable. :)
> Kudos to y
On Wed, Jun 15, 2005 at 08:27:58PM -0400, Jeff Squyres wrote:
> On Jun 15, 2005, at 7:02 PM, Ben Allan wrote:
>
> Ah -- I thought that that would be a different issue (I presume you're
> speaking of the compile/lib flags command, like gnome-config et
> al.)...? Are you saying that the compile/l
On Jun 15, 2005, at 7:02 PM, Ben Allan wrote:
The ompi_info command was directly derived from the LAM/MPI laminfo
command. However, I've never liked the fact that there's a "_" in the
name. Should it be renamed? Options I see are:
I, for obvious reasons (mainly to do with 'well, most projec
[an aside for the mailing list admin before the main message:
I want to subscribe a secondary address
and then check the box that
says nomail in the mailman membership list.
The secondary address can post mail but runs no
server to accept inbound mail, which tends to squish
the confirm portion of
On Jun 15, 2005, at 6:07 PM, Jeff Squyres wrote:
bin/ompi_info presents an opportunity to help all us shlubs that
have to do gnu build systems.
BTW, I forgot to mention -- try running "ompi_info -all" and/or
"ompi_info -all -parsable". It is explicitly aimed at those who need
to query the c
On Jun 15, 2005, at 3:51 PM, Benjamin Allan wrote:
bin/ompi_info presents an opportunity to help all us shlubs that
have to do gnu build systems.
Heh. So you got a bootleg Open MPI tarball after all! :-) (I'm
actually in the middle of replying to your other post -- sometimes it
takes me a
11 matches
Mail list logo
