Nils,
I find that this is most easily resolved by simply specifying the name
of your C compiler. For instance, you can set environment variable CC
for a single command by doing the following:
$ CC=/opt/mpich/bin/mpicc ./configure --with-python=python2.3
Otherwise you could try adding the --with-libs option and specifying
where your mpich libraries are in addition to specifying the include
path.
However, I find that simply setting CC is much easier and reproducable
across systems. Given that mpicc is usually already in the users
path, they can just do
$ CC=mpicc ./configure and expect the configure to work.
One other thing worth mentioning is that if you want to use pyMPI
interactively you made need to specify --with-isatty and/or
--with-prompt-nl at configure time. Keep this in mind if you run into
problems with interactive mode.
~Mike
On Wed, 08 Dec 2004 10:13:01 -0800,
pym...@li...
<pym...@li...> wrote:
> Date: Wed, 08 Dec 2004 15:02:02 +0100
> From: Nils Wagner <nw...@me...>
> Organization: Institute A of Mechanics
> To: pym...@li...
> Subject: [Pympi-users] WARNING: MPI must need some more libraries...
>
> Hi all,
>
> I am going to install pyMPI-2.0b0.
>
> ./configure --with-includes=/opt/mpich/include --with-python=python2.3
>
> yields a warning
>
> configure: WARNING: MPI must need some more libraries... Look at
> config.log. You may need to add --with-libs info
>
> Which additional libraries must be included ?
>
> Any pointer would be appreciated.
>
> Nils
>
> A make in /var/tmp/pyMPI-2.0b0 yields
>
> snip
|
