1 |
On 13/12/12 20:36, Fabian Groffen wrote: |
2 |
> On 13-12-2012 10:15:35 +1300, François Bissey wrote: |
3 |
>> Hi, |
4 |
>> |
5 |
>> I am puzzled by a problem I suddenly have emerging dev-python/sympy |
6 |
>> in my prefix on OS X 10.5.8: |
7 |
>> * Building of dev-python/sympy-0.7.2 with CPython 2.7... |
8 |
>> python2.7 setup.py build -b build-2.7 |
9 |
>> python2.7(34113) malloc: *** error for object 0x29f10b0: Non-aligned pointer |
10 |
>> being freed (2) |
11 |
>> *** set a breakpoint in malloc_error_break to debug |
12 |
>> Assertion failed: (ob_refcnt == 0), function ~PythonExtensionBase, file |
13 |
>> CXX/Python2/cxx_extensions.cxx, line 1320. |
14 |
>> /Users/frb15/Desktop/Gentoo/var/tmp/portage/dev- |
15 |
>> python/sympy-0.7.2/temp/environment: line 1208: 34113 Abort trap |
16 |
>> "$(PYTHON)" "${setup_file#*|}" "${_DISTUTILS_GLOBAL_OPTIONS[@]}" build -b |
17 |
>> "$(_distutils_get_build_dir)" "$@" |
18 |
>> |
19 |
>> The funny thing is, if I go into the build directory and execute |
20 |
>> python2.7 setup.py build -b build-2.7 |
21 |
>> everything works fine. I am supposing that some environment is messing up with |
22 |
>> the ebuild. Any ideas? Does it need to be ported to python-r1 in short order? |
23 |
>> All other python packages I tried have been fine. |
24 |
> |
25 |
> Please do me a favour, and try disabling sandbox feature and re-emerge |
26 |
> it. It shouldn't make a difference, but well ... you never know. |
27 |
> |
28 |
> |
29 |
It seems it must have been a problem with my install of sage from the |
30 |
sage-on-gentoo overlay (I am the main committer there and try to have |
31 |
the thing working on prefix too). Now that I have completed a full |
32 |
upgrade it emerges like a charm. |
33 |
Just for the record on why sage is relevant here: sage uses sympy |
34 |
(runtime) if sage is present sympy uses bits of it (runtime detection), |
35 |
so things are a bit circular. But there is more! sympy imports itself at |
36 |
install time.... |
37 |
|
38 |
Francois |