On Jan 6, 2009, at 4:36 PM, Ethan Mallove wrote:
Can the Open MPI configure setup handle ${exec_prefix} at the command
line? ${exec_prefix} seems to be getting eval'd to "NONE" in the
sub-configure's, and I get the following error:
...
*** GNU libltdl setup
configure: OMPI configuring in opa
On Tue, Jan/06/2009 10:33:31AM, Ethan Mallove wrote:
> On Mon, Jan/05/2009 10:14:30PM, Brian Barrett wrote:
> > Sorry I haven't jumped in this thread earlier -- I've been a bit behind.
> >
> > The multi-lib support worked at one time, and I can't think of why it would
> > have changed. The one co
On Mon, Jan/05/2009 10:14:30PM, Brian Barrett wrote:
> Sorry I haven't jumped in this thread earlier -- I've been a bit behind.
>
> The multi-lib support worked at one time, and I can't think of why it would
> have changed. The one condition is that libdir, includedir, etc. *MUST* be
> specified
Sorry I haven't jumped in this thread earlier -- I've been a bit behind.
The multi-lib support worked at one time, and I can't think of why it
would have changed. The one condition is that libdir, includedir,
etc. *MUST* be specified relative to $prefix for it to work. It looks
like you w
I honestly haven't thought through the ramifications of doing a multi-
lib build with OPAL_PREFIX et al. :-\
If you setenv OPAL_LIBDIR, it'll use whatever you set it to, so it
doesn't matter what you configured --libdir with. Additionally mca/
installdirs/config/install_dirs.h has this by de
On Thu, Dec/25/2008 08:12:49AM, Jeff Squyres wrote:
> It's quite possible that we don't handle this situation properly. Won't
> you need to libdir's (one for the 32 bit OMPI executables, and one for the
> 64 bit MPI apps)?
I don't need an OPAL environment variable for the executables, just a
si
It's quite possible that we don't handle this situation properly.
Won't you need to libdir's (one for the 32 bit OMPI executables, and
one for the 64 bit MPI apps)?
On Dec 23, 2008, at 3:58 PM, Ethan Mallove wrote:
I think the problem is that I am doing a multi-lib build. I have
32-bit lib
On Tue, Dec/23/2008 02:33:07PM, Jeff Squyres wrote:
> Yes, it works for me... :-\
>
> With initial install dir of /home/jsquyres/bogus (in my $path and
> $LD_LIBRARY_PATH already):
>
> [11:30] svbu-mpi:~/mpi % mpicc hello.c -o hello
> [11:30] svbu-mpi:~/mpi % mpirun -np 2 hello
> stdout: Hello, w
Yes, it works for me... :-\
With initial install dir of /home/jsquyres/bogus (in my $path and
$LD_LIBRARY_PATH already):
[11:30] svbu-mpi:~/mpi % mpicc hello.c -o hello
[11:30] svbu-mpi:~/mpi % mpirun -np 2 hello
stdout: Hello, world! I am 0 of 2 (svbu-mpi.cisco.com)
stdout: Hello, world!
Can anyone get OPAL_PREFIX to work on Linux? A simple test is to see
if the following works for any mpicc/mpirun:
$ mv /tmp/foo
$ set OPAL_PREFIX /tmp/foo
$ mpicc ...
$ mpirun ...
If you are able to get the above to run successfully, I'm interested
in your config.log file.
Thanks,
Ethan
Hello,
The below FAQ lists instructions on how to use a relocated Open MPI
installation:
http://www.open-mpi.org/faq/?category=building#installdirs
On Solaris, OPAL_PREFIX and friends (documented in the FAQ) work for
me with both MPI (hello_c) and non-MPI (hostname) programs. On Linux,
I can o
11 matches
Mail list logo
