Compilation error building sfepy

46 views
Skip to first unread message

Tom Aldcroft

unread,
Jan 17, 2012, 11:03:08 AM1/17/12
to sfepy...@googlegroups.com
Hi -

I'm trying to build SfePy on a CentOS-5 x86_64 machine. I'm using
Python 2.7 which has the mandatory dependencies stated in the INSTALL
file. I don't yet have all the optional dependencies but thought I
would try to just get started with the simplest build strategy. The
compiler is gcc 4.1.2. A full log of the output from "python setup.py
build_ext --inplace" is in the following paste:

http://paste.pocoo.org/show/536250/

The error is:

...
compiling C sources
C compiler: gcc -pthread -fno-strict-aliasing -fPIC -g -O2 -DNDEBUG -g
-fwrapv -O3 -Wall -Wstrict-prototypes -fPIC

compile options: '-D__SDIR__='"sfepy/fem/extmods"' -DSFEPY_PLATFORM=0
-D__SDIR__='"sfepy/fem/extmods"' -DSFEPY_PLATFORM=0
-Isfepy/fem/extmods
-I/proj/sot/ska/dev/arch/x86_64-linux_CentOS-5/lib/python2.7/site-packages/numpy/core/include
-I/proj/sot/ska/dev/arch/x86_64-linux_CentOS-5/include/python2.7 -c'
extra options: '-g -O2'
gcc: sfepy/fem/extmods/mappings.c
sfepy/fem/extmods/mappings.c: In function
\u2018__pyx_pf_5sfepy_3fem_7extmods_8mappings_14CVolumeMapping___cinit__\u2019:
sfepy/fem/extmods/mappings.c:1116: error: incompatible types in assignment
sfepy/fem/extmods/mappings.c:1190: error: incompatible types in assignment
sfepy/fem/extmods/mappings.c:1264: error: incompatible types in assignment
sfepy/fem/extmods/mappings.c: In function
\u2018__pyx_pf_5sfepy_3fem_7extmods_8mappings_15CSurfaceMapping___cinit__\u2019:
...
<AND MORE LIKE THIS>

Any ideas on the source of this problem? I thought about trying to
build on a more modern OS, but eventually I'll need to run this on
CentOS-5.

Thanks,
Tom

Md. Golam Rashed

unread,
Jan 17, 2012, 1:05:51 PM1/17/12
to sfepy...@googlegroups.com, tald...@cfa.harvard.edu
Hi tom,
get the EPD from enthought, its free for academic use.
download the Linux package and install. then try to build sfepy again.
(either epd-7.2-2-rh5-x86.sh  or epd-7.2-2-rh5-x86_64.sh depending on your architecture)

Tom Aldcroft

unread,
Jan 17, 2012, 1:45:38 PM1/17/12
to sfepy...@googlegroups.com

Great, that did the trick. My normal Python distribution is actually
ActivePython underneath, so it's interesting that there is some build
issue.

BTW, "make clean" and even "rm -rf build" were apparently insufficient
to really clean the build. This doesn't quite make sense, but I'll
say that after these steps I tried building with EPD and it failed
with exactly the same error. So out of desperation I started fresh
from the source tarball and *then* it worked with EPD.

Anyway, now hopefully I can start learning SfePy.

Thanks,
Tom


> --
> You received this message because you are subscribed to the Google Groups
> "sfepy-devel" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/sfepy-devel/-/JlUCve3HwXUJ.
> To post to this group, send email to sfepy...@googlegroups.com.
> To unsubscribe from this group, send email to
> sfepy-devel...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/sfepy-devel?hl=en.

Robert Cimrman

unread,
Jan 18, 2012, 4:04:09 AM1/18/12
to sfepy...@googlegroups.com
On 01/17/12 19:45, Tom Aldcroft wrote:
> On Tue, Jan 17, 2012 at 1:05 PM, Md. Golam Rashed
> <rashed...@gmail.com> wrote:
>> Hi tom,
>> get the EPD from enthought, its free for academic use.
>> http://download.enthought.com/epd_7.2/
>> download the Linux package and install. then try to build sfepy again.
>> (either epd-7.2-2-rh5-x86.sh or epd-7.2-2-rh5-x86_64.sh depending on your
>> architecture)
>
> Great, that did the trick. My normal Python distribution is actually
> ActivePython underneath, so it's interesting that there is some build
> issue.
>
> BTW, "make clean" and even "rm -rf build" were apparently insufficient
> to really clean the build. This doesn't quite make sense, but I'll
> say that after these steps I tried building with EPD and it failed
> with exactly the same error. So out of desperation I started fresh
> from the source tarball and *then* it worked with EPD.

Glad to hear you managed to build it. As for the original error, it occurred in
a cython-generated C code, so it might have been some cython-gcc version
incompatibility.

"make clean" is an alias to "python setup.py clean" but there is a "stronger"
command, namely "python setup.py clean --all", which should really clean
everything.

> Anyway, now hopefully I can start learning SfePy.

Great, do not hesitate to ask here in case of problems!

Cheers,
r.

Reply all
Reply to author
Forward
0 new messages