Re: Sage build failure (off-topic?)

Kal. Mar. MMX AUC quidam/quædam/quoddam 'Christopher Schwan' inquit:

> Hi Peter,
>
> On Monday 01 March 2010 18:50:32 Peter Gantner wrote:
>> Hi Francois,
>>
>> Weel, I'll leave the discussion of my failure on here for the time being
>> then.
>>
>> Hodie pr. Kal. Mar. MMX AUC  quidam 'François Bissey' inquit:
>>> Not seen that before, what is the version of python you use?
>>> emerge --info could be good as well.
>>
>> Python is:
>> * dev-lang/python-2.6.4-r99
>>     Install date: Fri Jan 29 19:08:38 2010
>>     USE="ipv6 sqlite ssl tk --berkdb -build -doc -elibc_uclibc -examples
>> -gdbm -+ncurses -+readline -+threads -+wide-unicode -wininst -+xml"
>> CFLAGS="-O2 -march=nocona -mtune=native -pipe -w -fomit-frame-pointer
>> -momit-leaf-frame-pointer"
>>
>> which is from sage-on-gentoo.
>>
>> emerge --info is attached.
>>
>> Let me know whatever info you need more.
>>
>> Greets,
>>    Peter G.
>
> you could try to compile Sage with portage's original python:
>
> emerge -1 =dev-lang/python-2.6.4-r1
> emerge sage

Ah, the simple solution worked! Python from portage did the trick.

I don't know why I never tried that, I guess because I thought if 
there's a version in the overlay it will have some stuff patched in 
which is required by sage.

Abyway If you can think of something I can do to narrow down the problem 
with the overlay version let me know.

Now I shall test out my brand new sage install!

Thanks,
   Peter

--

-- 
Some people, when confronted with a problem, think "I know,
I'll use regular expressions." Now they have two problems.
    -- Jamie Zawinski