Re: build problem with intel compiler

I'm using the Enthought Python Distribution version 7.1-1 (64bit), which is
supposedly built with Intel compilers and MKL (PyNIO works with Intel). Do you
think that may cause problems?

On March 26, 2012 01:50:14 PM Mary Haley wrote:
> I'm not sure why setting CC doesn't seem to be taking effect for the final
> load command, or why you are not getting -fPIC even though it is set.
>
> At this point, you can try editing setup.py directly, and forcing the
> environment variables to be set there. You can see how it's done for
> CFLAGS in that file, and do the same for CC, CFLAGS, etc. Just set these
> environment variables to the same ones you're using as before.
>
> The other possibility is that the python you are using might have been
> built in 32-bit, and it may be setting the compiler flags.
>
> Are you using a python that you compiled yourself with icc, or are you
> using a system python?
>
> --Mary
>
> On Mar 23, 2012, at 9:26 AM, Andre R. Erler wrote:
> > Yes, I did verify that they are set, and I certainly set them in the same
> > shell.
> > The environment variables are being seen in the compilation step, but
> > linking is always done with gcc, matter how I set the environment
> > variables. Btw. according to the build output the -fPIC flag is set
> > during compilation, and that's why I really don't understand the error.
> > I suspect it is some compatibility issue between gcc and icc.
> > I've attached the log file.
> >
> > - Andre
> >
> > On March 23, 2012 11:13:31 AM Mary Haley wrote:
> >> Andre,
> >>
> >> Are you saying that you set all these environment variables, but that
> >> they have no effect? It's possible that these settings are not being
> >> "seen" by the PyNGL installation if they are not done in the same
> >> shell.
> >>
> >> Just before you type "python setup.py install" did you verify that all
> >> your environment variables were set as expected?
> >>
> >> --Mary
> >>
> >> On Mar 23, 2012, at 9:03 AM, Andre R. Erler wrote:
> >>> I've attached a text file with all the environment variables I'm using.
> >>> I read the page in your link and I have most of them from there, but
> >>> it seems there are more relevant environment variables but I wasn't
> >>> able to find a complete list.
> >>>
> >>> - Andre
> >>>
> >>> On March 23, 2012 09:57:07 AM Mary Haley wrote:
> >>>> Did you try setting the CC environment variable to the compiler you
> >>>> want?
> >>>>
> >>>> Please see:
> >>>>
> >>>> http://www.pyngl.ucar.edu/Download/build_pyngl_from_src.shtml#SetCompi
> >>>> le rEn vVars
> >>>>
> >>>> --Mary
> >>>>
> >>>> On Mar 22, 2012, at 1:20 PM, Andre R. Erler wrote:
> >>>>> As far as I am aware, PyNGL doesn't give me any configuration
> >>>>> options, so I don't know which options are used for PyNGL.
> >>>>> I used the same environment and compiler flags to build NCL/NCARG and
> >>>>> PyNGL. I built NCL/NCARG without PNG/libcairo-related stuff and
> >>>>> without HDF4 and HDF- EOS. There was no mention of requirements in
> >>>>> the readme so I didn't think this was a problem.
> >>>>>
> >>>>> - Andre
> >>>>>
> >>>>> On March 21, 2012 11:46:14 PM Mary Haley wrote:
> >>>>>> It looks like NCL wasn't built with the same options as PyNGL.
> >>>>>>
> >>>>>> How did you build NCL? What options did you use?
> >>>>>>
> >>>>>> --Mary
> >>>>>>
> >>>>>> On Mar 19, 2012, at 5:39 PM, Andre R. Erler wrote:
> >>>>>>> Hi All,
> >>>>>>> I've posted to this list earlier. I made some progress building
> >>>>>>> PyNio and now I need to build PyNGL itself. Unfortunately I'm
> >>>>>>> getting a rather strange error message.
> >>>>>>> I'm running a 64bit kubuntu 11.04 system and I built NCARG/NCL and
> >>>>>>> all the dependencies as well as PyNIO with the Intel Compiler Suite
> >>>>>>> (composerxe-2011.4.191). I don't have HDF4 or libcairo and built
> >>>>>>> NCARG and PyNGL without these options.
> >>>>>>> The error is this:
> >>>>>>>
> >>>>>>> /usr/bin/ld: /usr/local/ncarg/lib/libnfpfort.a(dmapgci.o):
> >>>>>>> relocation R_X86_64_32 against `.rodata.str1.4' can not be used
> >>>>>>> when making a shared object; recompile with -fPIC
> >>>>>>> /usr/local/ncarg/lib/libnfpfort.a: could not read symbols: Bad
> >>>>>>> value collect2: ld returned 1 exit status
> >>>>>>> error: Command "gcc -pthread -shared -g -L/usr/local/lib
> >>>>>>> -L/usr/lib32/ -O2 - I/usr/local/include -I/usr/include/xorg/
> >>>>>>> build/temp.linux-x86_64-2.7/Helper.o
> >>>>>>> build/temp.linux-x86_64-2.7/hlu_wrap.o
> >>>>>>> build/temp.linux-x86_64-2.7/gsun.o - L/usr/local/ncarg/lib
> >>>>>>> -L/opt/intel/composerxe-2011.4.191/compiler/lib/intel64/
> >>>>>>> -L/opt/EPD/epd-7.1-1-rh5-x86_64/lib -lnfpfort -lhlu -lncarg
> >>>>>>> -lncarg_gks - lncarg_c -lngmath -lX11 -lm -lifcore -lirc -lifport
> >>>>>>> -lpython2.7 -o build/lib.linux-x86_64-2.7/PyNGL/_hlu.so" failed
> >>>>>>> with exit status 1
> >>>>>>>
> >>>>>>> I have no idea why this happens or how to fix it. I included -fPIC
> >>>>>>> in all compiler flags and I'm also wondering why gcc does the
> >>>>>>> linking even though all the compilation is done with icc/ifort.
> >>>>>>> I've attached a script with my environment variables and the
> >>>>>>> build-log. Any help would be greatly appreciated.
> >>>>>>> <log.setup.py><installPyNGL.sh>____________________________________
> >>>>>>> __ __ __ _____ pyngl-talk mailing list
> >>>>>>> List instructions, subscriber options, unsubscribe:
> >>>>>>> http://mailman.ucar.edu/mailman/listinfo/pyngl-talk
> >>>
> >>> <installPyNGL.sh>
> >
> > <log.setup.py>
Received on Mon Mar 26 12:48:10 2012