LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: Jerome BENOIT (jgmbenoit_at_[hidden])
Date: 2003-05-07 02:15:47


Yesterday,
I noticed something which may be realted to this minor issue:
I made a new build with

--prerfix=/usr/local --enbale-shared --disable-static [...]

and it appeared that some lib files are installed in

/usr/local/lib

and others in

/usr/local/lib/lam

This point leads to guess that there should be a misusage
of pkgWHATEVERdir and WHATEVERdir.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>.
>I have noticed some minor strange behaviours at the building/installing
> stage: as the headers were not in one `lam' directory (but dispatched in
> the regular `/usr/local/include' ) at my first try,
> I added --includedir=/usr/local/include/lam to `./configure ':
> the headears are now at the right place,
> but, surprise,
> the wrappers think that the header are in `/usr/local/include'
> but not in `/usr/local/include/lam'.

Excellent catch!

I believe that this happens in 6.5.x as well. However, this is easily
fixable (I think we simply made a bad assumption in the wrapper compilers
to -I$prefix/include instead of -I$includedir). I'd be willing to bet
that we did the same thing with -L$prefix/lib instead of -L$libdir, too.
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

I hope that helps,
Jerome