Path oddity in PNetCDF build/configure

[Wei-Keng Liao]

Please let me know the configure command used.

Wei-keng

On Oct 24, 2021, at 1:29 PM, Carl Ponder <cponder at nvidia.com<mailto:cponder at nvidia.com>> wrote:


This is in a Dockerfile rather than my usual bash scripting.
Here's the PATH being printed during the build
Step 95/156 : RUN echo ${PATH}
 ---> Running in 8586a4aef68a
/usr/local/nvidia/bin:/usr/local/cuda/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/bin:/usr/local/cuda/bin:/usr/local/pgi/Linux_x86_64/21.9/compilers/bin
And the mpicc location tests correctly:
Step 95/155 : RUN which mpicc
 ---> Running in e2161d554278
/usr/local/bin/mpicc
________________________________
Subject:        Re: Path oddity in PNetCDF build/configure
Date:   Sun, 24 Oct 2021 16:32:42 +0400
From:   Bruno Pagani <bruno.pagani at astrophysics.eu><mailto:bruno.pagani at astrophysics.eu>
To:     Carl Ponder <cponder at nvidia.com><mailto:cponder at nvidia.com>, Wei-keng Liao <wkliao at eecs.northwestern.edu><mailto:wkliao at eecs.northwestern.edu>
CC:     parallel-netcdf at lists.mcs.anl.gov<mailto:parallel-netcdf at lists.mcs.anl.gov>


External email: Use caution opening links or attachments

How do you set PATH? Did you quote it? Seems somehow your path end up being yes, likely due to expansion of its previous value.


________________________________
Le 24 octobre 2021 16:30:03 GMT+04:00, Carl Ponder <cponder at nvidia.com><mailto:cponder at nvidia.com> a écrit :
When I build PNetCDF with MPICC=mpicc and mpicc on my $PATH, I see this during the configure phase:
ENV PATH=${PATH}:/usr/local/bin
ENV MPICC mpicc
...
checking for sed handling option -i ... /usr/bin/sed -i''
checking mpicc under yes... no
configure: error:
   -----------------------------------------------------------------------
     Specified MPI C compiler "mpicc" cannot be found under yes
     PnetCDF requires a working MPI C compiler. Please specify the location
     of an MPI C compiler, either in the MPICC environment variable
     (not CC variable) or through --with-mpi configure flag. Abort.
   -----------------------------------------------------------------------
I can work around it by making the path absolute
ENV MPICC /usr/local/bin/mpicc
...
checking for sed handling option -i ... /usr/bin/sed -i''
checking whether /usr/local/bin/mpicc exists and is executable... yes
But, based on the first message, I'm thinking there's an incorrect path-search during the configure phase.
This is with PNetCDF 1.12.2.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/parallel-netcdf/attachments/20211024/67ea5c6d/attachment.html>