[sage-support] Re: SnapPeaPython

2008-09-12 Thread hypermonkey2
success! i installed the missing packages and it runs fine! That is, without error... it is dissapointingly slow, however. oh well, thanks much! Jon On Sep 11, 5:21 am, Adam Webb <[EMAIL PROTECTED]> wrote: > Hi, > > On Sep 11, 3:05 am, hypermonkey2 <[EMAIL PROTECTED]> wrote: > > > > > > > Cool!

[sage-support] Re: SnapPeaPython

2008-09-11 Thread Adam Webb
Hi, On Sep 11, 3:05 am, hypermonkey2 <[EMAIL PROTECTED]> wrote: > Cool! i actually did not have gcc, but i installed it now. my error > looks like now: > >  [1;31meeepc-jonathanl: [1;34m/media/E/SnapPeaPython [1;00m> python > setup.py build > running build > running build_py > running build_ext

[sage-support] Re: SnapPeaPython

2008-09-10 Thread Robert Bradshaw
On Sep 10, 2008, at 5:48 PM, mabshoff wrote: > On Sep 10, 5:45 pm, hypermonkey2 <[EMAIL PROTECTED]> wrote: >> Hi again! > > Hi, > >> i am trying to get SnapPeaPython running in SAGE on my EEEpc >> (on an SD card (ext2)). > > Don't do it the following way since you are installing into to > "global

[sage-support] Re: SnapPeaPython

2008-09-10 Thread hypermonkey2
Cool! i actually did not have gcc, but i installed it now. my error looks like now: [1;31meeepc-jonathanl: [1;34m/media/E/SnapPeaPython [1;00m> python setup.py build running build running build_py running build_ext building 'SnapPea.SnapPeaC' extension gcc -pthread -fno-strict-aliasing -DNDEBUG

[sage-support] Re: SnapPeaPython

2008-09-10 Thread mabshoff
On Sep 10, 5:45 pm, hypermonkey2 <[EMAIL PROTECTED]> wrote: > Hi again! Hi, > i am trying to get SnapPeaPython running in SAGE on my EEEpc > (on an SD card (ext2)). Don't do it the following way since you are installing into to "global" Python. >  [1;31meeepc-jonathanl: [1;34m/media/E/SnapPe

[sage-support] Re: SnapPeaPython

2008-09-10 Thread Mike Hansen
Hello, On Wed, Sep 10, 2008 at 5:45 PM, hypermonkey2 <[EMAIL PROTECTED]> wrote: > unable to execute gcc: No such file or directory > error: command 'gcc' failed with exit status 1 > > any ideas where this gcc problem comes from? It looks like you don't have gcc installed on your system. --Mike