Hi Neil,
Since the configure process is executed in the front end which is a
Linux system,
configure naturally thinks it is working in a Linux system, therefore it
goes to
the Linux configure settings. I think the right solution is to tell
configure to
build for a cross-compiling Cray
Albert,
On 5/7/2013 12:50 PM, Albert Cheng wrote:
Since the configure process is executed in the front end which is a
Linux system,
configure naturally thinks it is working in a Linux system, therefore
it goes to
the Linux configure settings. I think the right solution is to tell
configure
Here's how we build HDF5 1.8.x on our Cray XK6 for CLE:export CC=ccexport
CFLAGS=-O2 -h tolerant -h system_allocexport CXX=CCexport CXXFLAGS=-O2 -h
tolerant -h system_allocexport F77=ftnexport F90=ftnexport F9X=ftnexport
FFLAGS=-O2 -emexport RUNSERIAL=aprun -n 1 -N 1 -qexport
RUNPARALLEL=aprun -n
,
Neil.
View this message in context: Re: building hdf5-1.8.10-patch1:
H5_CFLAGS variable problems for Cray compiler
http://hdf-forum.184993.n3.nabble.com/building-hdf5-1-8-10-patch1-H5-CFLAGS-variable-problems-for-Cray
Hi Albert,
We are using a Cray XK6 running Cray's Compute Linux Environment (CLE) with
the Cray CCE compiler. The front end nodes run SLES Linux and the compute
nodes run CLE. So when building HDF5 (and any other application/library)
it's a cross compilation.
I can get the library to build
Hi again,
As promised, here is the version output information for the Cray compiler
(CCE). Note: this version information is obtained using the command: cc
-V.
cc -v and cc --version are not supported.
cc -V
/opt/cray/xt-asyncpe/5.17/bin/cc: INFO: Compiling with
CRAYPE_COMPILE_TARGET=native.
Cray
Hi Mohamad and Albert,
Thanks for the replies. I'll try out the 1.8.11 snapshot later this week and
let you know how I get on as well as looking at the version information
produced by the Cray compilers.
As it happens the cc, CC and ftn commands on the Cray (both under Catamount
and CLE) are all
Hi Neil,
I worked in a Cray about 3 to 4 years ago. Back then the cc and ftn were
actually cross compilers
provided by PGI. Maybe they are changed and supported by Intel.
One of our staff has more recent experience with Cray XE6,
Cray Linux Environment (CLE) PrgEnv-pgi/4.0.46
I managed to replicate the issue.
We test only with the default PGI compilers, which work quite fine.
However when I switch to the Cray compilers, I see the same issue you
guys are seeing.
We'll add it to our bug tracking system. Thanks for reporting!
Mohamad
On 4/26/2013 9:47 AM, Albert
Oh and please follow Albert's instructions about giving us more
information about your system and build failure.
More information = Better fix :-)
Thanks,
Mohamad
On 4/26/2013 9:56 AM, Mohamad Chaarawi wrote:
I managed to replicate the issue.
We test only with the default PGI compilers,
10 matches
Mail list logo
