[petsc-dev] UMFPACK + Intel compiler

[Garth N. Wells]

On Sat, Jan 5, 2013 at 5:20 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:
>
>
> On Sat, Jan 5, 2013 at 11:15 AM, Garth N. Wells <gnw20 at cam.ac.uk> wrote:
>>
>> Note quite sure how to delve into exactly what the compiler is doing,
>> but doing some printing from the Makefile right before the compiler is
>> first called:
>>
>>         @echo "Testing CFLAGS: $(CFLAGS)"
>>         @echo "Testing C:      $(C)"
>>         $(C) -DDINT -c ../Source/amd_aat.c -o amd_i_aat.o
>>
>> I get
>>
>>     Testing CFLAGS: -fPIC -wd1572 -mt_mpi -O3 -xHost -DUF_long=long
>> long -DUF_long_max=ULONG_MAX -DUF_long_id='%lld' -DNCHOLMOD
>>     Testing C:      mpicc -fPIC -wd1572 -mt_mpi -O3 -xHost
>> -DUF_long=long long -DUF_long_max=ULONG_MAX -DUF_long_id='%lld'
>> -DNCHOLMOD   -I../Include -I../../UFconfig
>>     mpicc -fPIC -wd1572 -mt_mpi -O3 -xHost -DUF_long=long long
>> -DUF_long_max=ULONG_MAX -DUF_long_id='"%lld"' -DNCHOLMOD
>> -I../Include -I../../UFconfig -DDINT -c ../Source/amd_aat.c -o
>> amd_i_aat.o
>>    icc: error #10236: File not found:  'long'
>
>
> Doesn't the same error occur with gcc? No. With gcc:

gcc is fine. So too, it turns out, is icc and mpiicc. There is
something up with mpicc on the system I'm using: mpicc -v

    mpiicc for the Intel(R) MPI Library 4.0 Update 3 for Linux*
    Copyright(C) 2003-2011, Intel Corporation.  All rights reserved.
    icc version 12.1.4 (gcc version 4.4.6 compatibility)

It wraps the same libraries as mpiicc: mpiicc -v

    mpiicc for the Intel(R) MPI Library 4.0 Update 3 for Linux*
    Copyright(C) 2003-2011, Intel Corporation.  All rights reserved.
    icc version 12.1.4 (gcc version 4.4.6 compatibility)

but a diff says that there some differences in the mpiicc and mpicc scripts.


> Do you have configure.log? What
> "make" is this using?
>

I drilled down to running it in

    externalpackages/UMFPACK-5.5.1/AMD/Lib

This is the first place at which a file is built.

Garth

>>
>> Double quotes don't seem to help. Changing 'long long' to 'long', it
>> builds fine.
>
>
> Unfortunately that doesn't work with LLP64 (like Windows).