← Back to team overview

oship-dev team mailing list archive

Re: oship install/buildout error

 

Devs -

I got OSHIP installed and working!  I ended up downloading a fresh tar of
python2.5.4 and compiled from source:

./configure --prefix=/home/charles/mypython2.5.4
exec-prefix=/home/charles/mypython2.5.4
make
make altinstall

Then to configure easy_install and virtualenv I performed:

wget http://peak.telecommunity.com/dist/ez_setup.py
./python ez_setup.py
easy_install virtualenv

All of the install steps after this worked flawlessly!

Thank you all!

- Charles




On Tue, Oct 20, 2009 at 7:03 PM, Roger Erens <roger@xxxxxxxxxxxxxxxxx>wrote:

> Hi Charles,
>
> I installed the Sabayon linux-distro within a virtual machine. It's
> Gentoo-based (Gentoo itself is too geeky/time-consuming for me to
> install).
> All I had to do is use Sulfur (a GUI frontend of Entropy?) to download
> python2.5 and bzr. It apparently already has g++ and the header-files
> installed. Then, I used the pre-installed easy_install (that goes
> along with system's python2.6) to install virtualenv. That reports
> version 1.3.4dev.
> As an aside, virtualenv --python=python2.6 --no-site-packages gives
> the same sort of line reporting that interpreter /usr/bin/python2.6 is
> already being used. Anyway:
>
> ~ $ virtualenv --python=python2.5 --no-site-packages oe
> creates a ~/oe/bin/activate command which I 'source'd
>
> Following that,
> (oe) ~/oe $ bzr branch lp:oship
> (oe) ~/oe $ cd oship/oship
> (oe) ~/oe/oship/oship $ python bootstrap.py
>
> works without segmentation faults. Also the rest of the installation
> goes smooth.
> Conclusion: installing on Gentoo should be possible, too.
>
> Good luck with your tests,
>
> Roger
>

References