[gmx-users] Re: Header present but cannot be compiled

[DimitryASuplatov]

OK,
I`ve solved the issue myself.

The problem disappears after passing -no-gcc option to icc compiler.

I`ve found some explanation here
http://software.intel.com/en-us/forums/intel-c-compiler/topic/59886.
In my understanding this wont work for all other programs but it
definitely works for as.
SDA  


On Tue, 2008-11-04 at 12:46 +0300, DimitryASuplatov wrote:
> Hello,
> I compile gromacs-4 on opensuse 11 2.6.25.5-1.1-default for
> core2quadro with intel cc version 10.1.
> Configure script threws the following warnings:
> 
> checking rpc/rpc.h usability... no
> checking rpc/rpc.h presence... yes
> configure: WARNING: rpc/rpc.h: present but cannot be compiled
> configure: WARNING: rpc/rpc.h:     check for missing prerequisite headers?
> configure: WARNING: rpc/rpc.h: see the Autoconf documentation
> configure: WARNING: rpc/rpc.h:     section "Present But Cannot Be Compiled"
> configure: WARNING: rpc/rpc.h: proceeding with the preprocessor's result
> configure: WARNING: rpc/rpc.h: in the future, the compiler will take precedence
> configure: WARNING:     ## ------------------------------------ ##
> configure: WARNING:     ## Report this to gmx-users at gromacs.org ##
> configure: WARNING:     ## ------------------------------------ ##
> checking for rpc/rpc.h... yes
> 
> and
> 
> checking limits.h usability... no
> checking limits.h presence... yes
> configure: WARNING: limits.h: present but cannot be compiled
> configure: WARNING: limits.h:     check for missing prerequisite headers?
> configure: WARNING: limits.h: see the Autoconf documentation
> configure: WARNING: limits.h:     section "Present But Cannot Be Compiled"
> configure: WARNING: limits.h: proceeding with the preprocessor's result
> configure: WARNING: limits.h: in the future, the compiler will take precedence
> configure: WARNING:     ## ------------------------------------ ##
> configure: WARNING:     ## Report this to gmx-users at gromacs.org ##
> configure: WARNING:     ## ------------------------------------ ##
> checking for limits.h... yes
> 
> 
> The autoconf site says that this is a problem of calling a
> preprocessor instead of compiler. I use default cpp for preprocessor.
> 
> Has anybody ever solved this problem?
> 
> Thanks