On Jan 26, 2006, at 4:53 PM, Jonathan Day wrote:
In which case, the solution would seem to have a
metafile containing the flags, the environment
variable they set/unset, the default value and what
software is required, as a simple table.
That might be possible, but it would be no small task.
I'm not entirely sure what the problem is with the
--with/--without flags. Within the configure script,
these flags enable/disable the setting of certain
environment variables and/or the running of certain
tests.
Within the RPM spec file, these need to be given,
sure, but in many cases there will
On Jan 25, 2006, at 6:32 PM, Daryl W. Grunau wrote:
Is there a more scalable way to do this, perchance?
I was trying to make the option-generator into a function which
could be
called in the %description section or in the %configure line so you'd
only need to maintain one area. I haven't f
> Date: Thu, 19 Jan 2006 13:19:42 -0500
> From: Jeff Squyres
> Subject: Re: [O-MPI users] ompi spec file
> To: Open MPI Users
> Message-ID: <23849e6b-b0ff-4eeb-84dc-4a01d72f8...@open-mpi.org>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
David --
Many thanks for this; I learned some new RPM tricks in here. :-)
I love the "--with ..." interface. The only thing that concerns me
is the scalability -- we have to add two things for each --with/--
enable option that we have for configure. Granted, we probably won't
be adding t
Hi, I realize there exists an RPM spec file distributed with OMPI tarball
but I've found it to be broken on several counts (e.g. a not-so-advertized
'feature' of spec files is that nested %if statements are unpredictable at
best) so I'm inlining one that I've been using successfully for quite some
