Re: [OMPI users] Wrappers should put include path *after* user args

2010-01-28 Thread Jeff Squyres
Sorry guys -- this one slipped off the radar. You're right that it didn't make it into v1.4.1. Short version - I looked into this yesterday and chatted with some other OMPI developers about it. We agree; we can move the user options up in the command line creation. I'll file a t

Re: [OMPI users] Wrappers should put include path *after* user args

2010-01-19 Thread Justin Bronder
On 04/12/09 16:20 -0500, Jeff Squyres wrote: > Oy -- more specifically, we should not be putting -I/usr/include on the > command line *at all* (because it's special and already included by the > compiler search paths; similar for /usr/lib and /usr/lib64). We should have > some special case code

Re: [OMPI users] Wrappers should put include path *after* user args

2009-12-04 Thread Jed Brown
On Fri, 4 Dec 2009 16:20:23 -0500, Jeff Squyres wrote: > Oy -- more specifically, we should not be putting -I/usr/include on > the command line *at all* (because it's special and already included > by the compiler search paths; similar for /usr/lib and /usr/lib64). If I remember correctly, the is

Re: [OMPI users] Wrappers should put include path *after* user args

2009-12-04 Thread Jeff Squyres
Oy -- more specifically, we should not be putting -I/usr/include on the command line *at all* (because it's special and already included by the compiler search paths; similar for /usr/lib and /usr/lib64). We should have some special case code that looks for /usr/include and simply drops it. Le

[OMPI users] Wrappers should put include path *after* user args

2009-12-04 Thread Jed Brown
Open MPI is installed by the distro with headers in /usr/include $ mpif90 -showme:compile -I/some/special/path -I/usr/include -pthread -I/usr/lib/openmpi -I/some/special/path Here's why it's a problem: HDF5 is also installed in /usr with modules at /usr/include/h5*.mod. A new HDF5 cannot be