I see - I was trying to understand your question as I don't recall ever encountering such a request before - to my knowledge, we have never supported that option as it was never requested.
I don't know how hard it would be to implement, but it looks like something we could do for future releases, perhaps starting in the 1.7 series. I'll have to look into it and discuss with a few people here and then get back to you on it. On Sep 9, 2012, at 8:02 AM, Dmitry N. Mikushin <maemar...@gmail.com> wrote: > Dear Ralph, > > I'm working on trunk, or close to it. When configuring with > --program-prefix=someprefix I get: > > configure: WARNING: *** The Open MPI configure script does not support > --program-prefix, --program-suffix or --program-transform-name. Users > are recommended to instead use --prefix with a unique directory and > make symbolic links as desired for renaming. > configure: error: *** Cannot continue > > This is what I meant by "disabled". > > And how --enable-orterun-prefix-by-default is involved? We just need > an installation kept in separate folder to have uniquely named > user-level wrappers, e.g. mpicc -> prefix-mpicc, etc., which correctly > link to their local orte-wrapper. > > Thanks, > - D. > > 2012/9/9 Ralph Castain <r...@open-mpi.org>: >> >> On Sep 8, 2012, at 1:14 PM, "Dmitry N. Mikushin" <maemar...@gmail.com> wrote: >> >>> Dear all, >>> >>> Setting program prefix is disabled for OpenMPI compilation, could you >>> please explain why? >> >> I'm not sure I understand - setting the prefix is most definitely enabled >> and working. What version of OMPI are you concerned about? >> >>> >>> Consider we want to make a package containing OpenMPI packed together >>> with our open-source compiler, that is installable on arbitrary Linux >>> system. In this case, it would be very handy to add some program >>> prefix to guarantee no confusion with other possibly installed MPI >>> implementations visible through $PATH. >> >> >> Are you saying that --enable-orterun-prefix-by-default is inadequate? This >> is the reason it exists - to avoid path confusion. If something further is >> required, please let us know and we'll see what can be done. >> >> >>> >>> Thanks, >>> - D. >>> _______________________________________________ >>> devel mailing list >>> de...@open-mpi.org >>> http://www.open-mpi.org/mailman/listinfo.cgi/devel >> >> >> _______________________________________________ >> devel mailing list >> de...@open-mpi.org >> http://www.open-mpi.org/mailman/listinfo.cgi/devel > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel
