[Ocfs2-test-devel] [PATCH 05/11] ocfs2-test: Changed configure.in to built ocfs2-test RPM.
Joel Becker
Joel.Becker at oracle.com
Tue Nov 4 17:30:36 PST 2008
On Tue, Nov 04, 2008 at 12:08:39PM +0800, tristan.ye wrote:
> On Mon, 2008-11-03 at 19:35 -0800, Joel Becker wrote:
> > I'm thoroughly confused. If you installed it from a tarball,
> > there is no rpm, so why would you query rpm?
> The reason why i query the rpm here is to check the MPICC in two both
> cases,so it makes the MPICC visible no matter you use rpm or tarball.
configure.in should not be checking via rpm, just via PATH. The
user can specify an extra PATH if they like. We can even add --with-mpi
arguments.
The specfile for ocfs2-test, if we determine that it is the
right thing to do, can pass the appropriate PATH or --with-mpi to
configure.
Joel
--
"You can get more with a kind word and a gun than you can with
a kind word alone."
- Al Capone
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
More information about the Ocfs2-test-devel
mailing list