OSHIP Devs -
Let me start out by thanking you all for the help! : )
I started over from the beginning to make sure I haven't done
something wrong or skipped a step
I'm using python2.5 that was installed by my system, but is not the
default python anymore (2.6 is)
I installed easy_install manually using the correct python version and
then:
# easy_install-2.5 virtualenv
# cd /opt
# virtualenv --python=python2.5 --no-site-packages oshipenv
Already using interpreter /usr/bin/python2.5
New python executable in oshipenv/bin/python2.5
Also creating executable in oshipenv/bin/python
Installing setuptools............done.
# (oshipenv) cd oshipenv
# (oshipenv) source bin/activate
# (oshipenv) bzr co lp:oship
# (oshipenv) cd oship/oship
-- this section shows python version info:
(oshipenv) oship # which python
/opt/oshipenv/bin/python
(oshipenv) oship # ll /opt/oshipenv/bin/python
-rwxr-xr-x 1 root root 5356 Oct 20 10:03 /opt/oshipenv/bin/python*
(oshipenv) oship # python
Python 2.5.2 (r252, Jan 15 2009, 19:33:00)
[GCC 4.1.2 (Gentoo 4.1.2 p1.1)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> exit()
(oshipenv) oship # python bootstrap.py
Creating directory '/opt/oshipenv/oship/oship/eggs'.
Generated script '/opt/oshipenv/oship/oship/bin/buildout'.
Develop: '/opt/oshipenv/oship/oship/.'
Installing 'z3c.recipe.eggbasket'.
We have no distributions for z3c.recipe.eggbasket that satisfies
'z3c.recipe.eggbasket==0.4.3'.
Segmentation fault
(oshipenv) oship # bin/buildout -v
Develop: '/opt/oshipenv/oship/oship/.'
Installing 'z3c.recipe.eggbasket'.
We have no distributions for z3c.recipe.eggbasket that satisfies
'z3c.recipe.eggbasket==0.4.3'.
Segmentation fault
Answering specific questions:
Roger:
> The first run shows a strange place to put the eggs in. 1) Was
virtualenv invoked with > --no-site-packages?
This is because I ran virtualenv from a weird spot already inside of
site-packages (i did use --no-site-packages)... This second time I
ran through I ran this command in /opt which gives nicer paths
> 2) Do you have a .buildout/default.cfg hanging around with content
that interferes?
I do not have any extra buildout cfgs laying around anywhere..
Roberto:
> And when he tries to do the buildout in Plone, it's the custom 2.4
Python version (that comes > bundled with Plone) that is launched, not
the OSHIP-compatible, 2.5 one.
> Sorry for my initial mistake,
which explains why my Plone test was not a good test : )
> Gentoo? Oops, my bad! But in this case, things are much simpler to
explain: typing "python2.5 > bootstrap.py" instead of "python
bootstrap.py" launches the "main" 2.5 Python (instead of the >
"virtualenv" one), and that's why (some of?) his eggs get installed
to: > /lib/python2.5/site-packages/oshipenv/oship/oship/eggs (instead
of: ~/oshipenv/oship/oship/eggs, > as expected).
In this email in the section "-- this section shows python version
info:" I use the right python and still get the segmentation fault.
Thank you all!!
- Charles
2009/10/20 Roberto Siqueira <siqueira@xxxxxxxxxxxxxxx
<mailto:siqueira@xxxxxxxxxxxxxxx>>
Hi, Roger:
Gentoo? Oops, my bad! But in this case, things are much simpler
to explain: typing "python2.5 bootstrap.py" instead of "python
bootstrap.py" launches the "main" 2.5 Python (instead of the
"virtualenv" one), and that's why (some of?) his eggs get
installed to:
/lib/python2.5/site-packages/oshipenv/oship/oship/eggs (instead
of: ~/oshipenv/oship/oship/eggs, as expected).
And when he tries to do the buildout in Plone, it's the custom
2.4 Python version (that comes bundled with Plone) that is
launched, not the OSHIP-compatible, 2.5 one.
Sorry for my initial mistake,
Roberto.
Roger Erens a écrit :
2009/10/20 Roberto Siqueira <siqueira@xxxxxxxxxxxxxxx
<mailto:siqueira@xxxxxxxxxxxxxxx>>:
Hi, Tim:
A segmentation fault during the installation process
simply means that at
(e.g.) step N we are referencing/calling some module that
should've been
successfully compiled at step N-1, but failed. Indeed,
this is usually
caused by compatibility problems. Two quick remarks:
- Charles is following the generic (AKA #391) FAQ. Maybe
changing to the
Windows-specific one:
https://answers.launchpad.net/oship/+faq/664 would
help?
He is using Gentoo Linux.
- His default Python is apparently 2.4 (as used by Plone).
How was the 2.5
version installed -- is it a custom installation? Maybe
reinstalling/upgrading to the 2.5 one from here:
http://www.python.org/download/releases would solve these
compatibility
issues?
The first run shows a strange place to put the eggs in.
1)
Was virtualenv invoked with --no-site-packages?
2)
Do you have a .buildout/default.cfg hanging around with
content that interferes?
Roger
HTH,
Roberto.
Tim Cook a écrit :
Hi All,
We obviously have issues with installations on MS
platforms. Can
someone with experience in this area please step up and
addressee these? Even if they are to say that that we
not support the MS
Windows platform?
Open source communities are supposed to solve these issues
collectively.
I do not even use MS products. Roger; WTF;;;;
Either fix it or tell
me who to give access to the FAQs that can fix it.
Thanks,
Tim
On Mon, 2009-10-19 at 11:23 -0400, Charles O'Brien wrote:
Hello Tim! I am having an issue getting OSHIP
installed. I think
there may be an issue with z3c.recipe.eggbasket
0.4.3 and buildout.
Both versions are pretty new.
I am following these directions:
https://answers.launchpad.net/oship/+faq/391
trying to install OSHIP and I am getting a
'Segmentation fault' error.
I first had the error when I ran 'python bootstrap.py'
(oshipenv)flip oship # python2.5 bootstrap.py
Creating directory
'/usr/lib/python2.5/site-packages/oshipenv/oship/oship/eggs'.
Generated script
'/usr/lib/python2.5/site-packages/oshipenv/oship/oship/bin/buildout'.
Develop:
'/usr/lib/python2.5/site-packages/oshipenv/oship/oship/.'
Installing 'z3c.recipe.eggbasket'.
We have no distributions for z3c.recipe.eggbasket
that satisfies
'z3c.recipe.eggbasket==0.4.3'.
Segmentation fault
I moved on and tried to run buildout -v
Installing 'z3c.recipe.eggbasket'.
We have no distributions for z3c.recipe.eggbasket
that satisfies
'z3c.recipe.eggbasket==0.4.3'.
Segmentation fault
To further test, I added to a working Plone 3.2
buildout these lines:
[parts] ...
eggbasket
[eggbasket]
recipe = z3c.recipe.eggbasket
eggs = grok
url =
http://grok.zope.org/releaseinfo/grok-eggs-1.0.tgz
and get this slightly more verbose error when i
run buildout -v
install eggbasket
# bin/buildout -v install eggbasket
Installing 'z3c.recipe.eggbasket'.
Picked: z3c.recipe.eggbasket = 0.4.3
Getting required 'zc.recipe.egg==1.1.0'
We have the distribution that satisfies
'zc.recipe.egg==1.1.0'.
Unused options for buildout: 'eggs'
'deprecation-warnings'
'debug-mode' 'client1-address' 'zope-directory'
'client2-address'
'verbose-security' 'zcml' 'zeo-address'.
Installing eggbasket.
Installing 'grok'.
We have no distributions for grok that satisfies
'grok'.
Couldn't find index page for 'grok' (maybe
misspelled?)
Getting distribution for 'grok'.
eggbasket: Not all distributions are installed. A
tarball will be
downloaded.
eggbasket: Using already
downloaded
../buildout-cache/downloads/grok-eggs-1.0.tgz
eggbasket: Extracting tarball contents...
eggbasket: Installing eggs
to
/opt/Plone-3.2/zeocluster/../buildout-cache/eggs
which will take a
while...
Installing 'grok'.
We have no distributions for grok that satisfies
'grok'.
Getting distribution for 'grok'.
We have the distribution that satisfies
'setuptools==0.6c9'.
Running easy_install:
/opt/Plone-3.2/Python-2.4/bin/python "-c" "from
setuptools.command.easy_install import main;
main()" "-mUNxd"
"/opt/Plone-3.2/zeocluster/../buildout-cache/eggs/tmpFGmwmT"
"-Z" "-q"
"/opt/Plone-3.2/buildout-cache/downloads/dist/grok-1.0.tar.gz"
path=/opt/Plone-3.2/buildout-cache/eggs/setuptools-0.6c9-py2.4.egg
Segmentation fault
Any ideas what may be causing this? Should I try
using an earlier
version? Thank you for any information you can lend!
- Charles
------------------------------------------------------------------------
_______________________________________________
Mailing list: https://launchpad.net/~oship-dev
<https://launchpad.net/%7Eoship-dev>
Post to : oship-dev@xxxxxxxxxxxxxxxxxxx
<mailto:oship-dev@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~oship-dev
<https://launchpad.net/%7Eoship-dev>
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~oship-dev
<https://launchpad.net/%7Eoship-dev>
Post to : oship-dev@xxxxxxxxxxxxxxxxxxx
<mailto:oship-dev@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~oship-dev
<https://launchpad.net/%7Eoship-dev>
More help : https://help.launchpad.net/ListHelp
