From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2007-06-07 09:49:59
FWIW, you should be able to see exactly the same effect if you run
the IBM test suite configure outside of MTT -- this looks like a
configure/autoconf issue, not an MTT issue.
On Jun 7, 2007, at 9:40 AM, Sharon Melamed wrote:
> Hi Jeff,
>
> I have those two files in my node (see attachment)
> I don't know what the purpose of these file either but the configure
> script of the ibm test uses them (see lines 1177 - 1193 in the
> configure
> script)
>
> I'll try to remove them and see what happens.
>
> Thanks.
> Sharon.
>
> -----Original Message-----
> From: mtt-users-bounces_at_[hidden]
> [mailto:mtt-users-bounces_at_[hidden]] On Behalf Of Jeff Squyres
> Sent: Thursday, June 07, 2007 2:56 PM
> To: General user list for the MPI Testing Tool
> Subject: Re: [MTT users] Test build failure
>
> This is really weird -- you're invoking configure with the proper
> command line:
>
> ./configure CC=mpicc CXX=mpic++ F77=mpif77
>
> But somehow it's getting "gcc" for the C compiler instead of "mpicc",
> and therefore it can't find <mpi.h>.
>
> One thing that I notice in your config.log (and configure output)
> that I have not seen before is that at the very beginning of
> configure, it is loading up 2 "site" config files:
>
> configure: loading site script /usr/local/share/config.site
> configure: loading site script /usr/local/etc/config.site
>
> I wonder if these are somehow overriding your choice of CC and
> setting it back to gcc.
>
> What are these files? Do you need them? I have no similar files in
> my autoconf installations.
>
>
> On Jun 7, 2007, at 3:27 AM, Sharon Melamed wrote:
>
>> Hi Jeff,
>> Sorry for the delay. Attached the config.log from the last
>> compilation.
>>
>> Thanks.
>>
>> Sharon.
>>
>> -----Original Message-----
>> From: mtt-users-bounces_at_[hidden]
>> [mailto:mtt-users-bounces_at_[hidden]] On Behalf Of Jeff Squyres
>> Sent: Wednesday, June 06, 2007 2:50 PM
>> To: General user list for the MPI Testing Tool
>> Subject: Re: [MTT users] Test build failure
>>
>> Wow, that's weird. Your INI file looks ok.
>>
>> Can you dig down into the scratch directory and find the config.log
>> file that resulted from running this configure script? I'd like to
>> see what the specific error was that caused it to fail to find mpi.h.
>>
>>
>>
>> On Jun 6, 2007, at 7:39 AM, Sharon Melamed wrote:
>>
>>> Hi,
>>>
>>> I'm trying to run MTT version 2.1.
>>>
>>> In the test build phase, some of the builds fails. For example:
>>>
>>> The build output of the ibm test looks like this:
>>>
>>>
>>>
>>> Evaluating: ./configure CC=mpicc CXX=mpic++ F77=mpif77
>>>
>>> make
>>>
>>> Running command: /tmp/IhYOhJexxR
>>>
>>> OUT:configure: loading site script /usr/local/share/config.site
>>>
>>> OUT:configure: loading site script /usr/local/etc/config.site
>>>
>>> OUT:Configuring Open MPI/IBM test suite
>>>
>>> OUT:checking for a BSD-compatible install... OUT:(cached) OUT:/usr/
>>> bin/install -c
>>>
>>> OUT:checking whether build environment is sane... OUT:yes
>>>
>>> OUT:checking for gawk... OUT:(cached) OUT:gawk
>>>
>>> OUT:checking whether make sets $(MAKE)... OUT:(cached) OUT:yes
>>>
>>> OUT:checking build system type... OUT:(cached) OUT:x86_64-unknown-
>>> linux-gnu
>>>
>>> OUT:checking host system type... OUT:x86_64-unknown-linux-gnu
>>>
>>> OUT:checking for gcc... OUT:(cached) OUT:gcc
>>>
>>> OUT:checking for C compiler default output file name... OUT:a.out
>>>
>>> OUT:checking whether the C compiler works... OUT:yes
>>>
>>> OUT:checking whether we are cross compiling... OUT:no
>>>
>>> OUT:checking for suffix of executables... OUT:
>>>
>>> OUT:checking for suffix of object files... OUT:(cached) OUT:o
>>>
>>> OUT:checking whether we are using the GNU C compiler... OUT:
>>> (cached) OUT:yes
>>>
>>> OUT:checking whether gcc accepts -g... OUT:(cached) OUT:yes
>>>
>>> OUT:checking for gcc option to accept ANSI C... OUT:(cached)
>>> OUT:none needed
>>>
>>> OUT:checking for style of include used by make... OUT:GNU
>>>
>>> OUT:checking dependency style of gcc... OUT:(cached) OUT:gcc3
>>>
>>> OUT:checking whether we are using the GNU C++ compiler... OUT:
>>> (cached) OUT:yes
>>>
>>> OUT:checking whether mpic++ accepts -g... OUT:(cached) OUT:yes
>>>
>>> OUT:checking dependency style of mpic++... OUT:(cached) OUT:gcc3
>>>
>>> OUT:checking for mpif77... OUT:yes
>>>
>>> OUT:checking whether we are using the GNU Fortran 77 compiler...
>>> OUT:yes
>>>
>>> OUT:checking whether mpif77 accepts -g... OUT:yes
>>>
>>> OUT:checking for ranlib... OUT:(cached) OUT:ranlib
>>>
>>> OUT:checking for mpi.h... OUT:no
>>>
>>> OUT:configure: error: cannot continue -- cannot find <mpi.h>
>>>
>>> OUT:make: *** OUT:No targets specified and no makefile foundOUT:.
>>> Stop.
>>>
>>> Command complete, exit status: 2
>>>
>>>
>>>
>>> As you can see, the configure script cant find the mpi.h file.
>>>
>>> I have this problem in other builds as well.
>>>
>>>
>>>
>>> Attached my ini file.
>>>
>>>
>>>
>>> Can someone help?
>>>
>>>
>>>
>>> Thanks.
>>>
>>> Sharon.
>>>
>>> <sharon-test-2.1.ini>
>>> _______________________________________________
>>> mtt-users mailing list
>>> mtt-users_at_[hidden]
>>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>>
>>
>> --
>> Jeff Squyres
>> Cisco Systems
>>
>>
>> _______________________________________________
>> mtt-users mailing list
>> mtt-users_at_[hidden]
>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>> <config.log>
>> _______________________________________________
>> mtt-users mailing list
>> mtt-users_at_[hidden]
>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>
>
> --
> Jeff Squyres
> Cisco Systems
>
> _______________________________________________
> mtt-users mailing list
> mtt-users_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
> <config.site>
> _______________________________________________
> mtt-users mailing list
> mtt-users_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
-- Jeff Squyres Cisco Systems