Hi, Pavan! I think this could be solution, but as it looks like also source code and object files should be shipped to customers. Or my be I didn't notice configure option for intermediate build output :-) Solution with environment variable will decrease size of shipped package, since only final binaries and support files will be shipped. It may be more preferable solution when software installation script is not trivial. Eugene. ________________________________________ From: Pavan Balaji [[email protected]] Sent: Sunday, December 23, 2012 7:00 PM To: [email protected] Cc: Yauheni Zelenko Subject: Re: [mpich-discuss] Hard-coded path to mpiexec.hydra.conf (1.4, 1.5) Sorry about the delay in getting around to this. We were tied up with the mpich-3.0 release. I'm still missing the point of this environment variable. Once you have a pre-built mpich installation, you can install mpich in any location of your choosing using: % make install prefix=<foobar> This overrides the --prefix passed to configure. In this case, you should ship the prebuilt mpich to your customers and run the above "make install" command to place it in the right location. Some of our other vendor partners follow the same model as well. -- Pavan On 07/12/2012 12:46 PM US Central Time, Yauheni Zelenko wrote:

Hi, Pavan!

Thank you for help!

However will be good idea to disable check of file in install location at all.

Or there should be way to specify install location in run-time with environment variable or command-line option (OpenMPI uses OPAL_PREFIX and --prefix correspondingly).

Other files affected are mpi compilation scripts (mpicc, etc), MPE scripts, libtool generated files, packages, makefiles.

Easy way to check - to compile MPICH2 in your home directory, install it and grep installed files for your login name.

Eugene. ________________________________________ From: Pavan Balaji [[email protected]] Sent: Thursday, July 12, 2012 10:26 AM To: [email protected] Cc: Yauheni Zelenko Subject: Re: [mpich-discuss] Hard-coded path to mpiexec.hydra.conf (1.4, 1.5)

Thanks. I've fixed this in r10004. Now the priority order for the config file:

1. Command line

2. Environment variable

3. Home directory

4. Install directory

-- Pavan

On 07/11/2012 06:37 PM, Yauheni Zelenko wrote:

...

Hi!

Hydra always try to open mpiexec.hydra.conf file in original install path location in HYD_uii_mpx_get_parameters() if such file is not found in user's home directory.

We ship pre-built MPICH2 with our application to customers, where original install path is invalid.

I think will be good idea to rely on environment variable instead of hard-coded path.

Eugene. _______________________________________________ mpich-discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss

-- Pavan Balaji http://www.mcs.anl.gov/~balaji

_______________________________________________ mpich-discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss

-- Pavan Balaji http://www.mcs.anl.gov/~balaji