Hi Andrew, As a quick solution I would recommend you to try to wrap the proxy (into a shell script) and add architecture recognition/specific logic via something like "uname -m" + check for "k1om" (and execute corresponding binary). So hydra would run the script and the script would select an appropriate proxy binary. There are several ways but this one should be quick and work fine. BR, Dmitry -----Original Message----- From: Andrew Green [mailto:[email protected]] Sent: Friday, September 18, 2015 12:03 PM To: [email protected] Subject: [mpich-discuss] MPICH with heterogeneous architectures Hello, I've been trying to use MPICH2 with an application on the Intel Xeon Phi. I have two builds of MPICH2: one host-compatible and one MIC-compatible. So far I have only been able to run either only on the host or only on the MIC; I would ideally like to be able to run on both simultaneously. I can see what is going wrong: hydra tries to launch a proxy on the MIC which has been compiled for the host and therefore can't be executed. Is there any way to change this default behaviour? I tried changing the launch executable, but it didn't have the effect I wanted. Thanks for your help, Andrew -------------------------------------------------------------------- Joint Stock Company Intel A/O Registered legal address: Krylatsky Hills Business Park, 17 Krylatskaya Str., Bldg 4, Moscow 121614, Russian Federation This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss