View previous topic :: View next topic |
Author |
Message |
2thumbs n00b
Joined: 04 Jun 2003 Posts: 6 Location: Edmonton, AB Canada
|
Posted: Wed Jun 04, 2003 4:26 pm Post subject: psycopg build broken? |
|
|
ARGH /me pulls remaining hair out
I'm trying to use an old Ultra5 to run a few development Zopes on. Zope 2.6.1 on python2.1 seems to work really well. However, without a database connection, it's sort of useless. PostgreSQL 7.3.2 also seems to work peachy. The problem is, the python-postgres database adaptor psycopg, while it does build, it does not work. Running the test scripts that ship with psycopg results in "Bus error". Launching any Zopes with the database adaptor installed (zpsycopgda) causes the zdaemon to crash with SIGBUS.
This happens with any of the available psycopg ebuilds for both python2.2 (semi useless for Zope) and for Python 2.1. Building the latest official source (1.1.4) also dies.
I doubt the problem is with psycopg, since other people are using it successfully on Sparc architectures. The only things it really builds against is PostgreSQL, Egenix mx-date-time, and Python... so maybe the problem lies there.
Anyone have ideas on how to get psycopg working on Sparc64/Gentoo 1.4? |
|
Back to top |
|
|
2thumbs n00b
Joined: 04 Jun 2003 Posts: 6 Location: Edmonton, AB Canada
|
Posted: Wed Jun 04, 2003 9:36 pm Post subject: |
|
|
Hrmm well I installed Python 2.1, PostgreSQL 7.3.3, and mx-base from the official sources in their own little sandbox. That didn't seem to fix the problem. So it must be some wierd psycopg/gentoo interaction... since it seems to work fine on Debian Sparc/64.... odd |
|
Back to top |
|
|
2thumbs n00b
Joined: 04 Jun 2003 Posts: 6 Location: Edmonton, AB Canada
|
Posted: Thu Jun 05, 2003 2:27 pm Post subject: |
|
|
Maybe someone here (that's using an UltraSparc) could build psycopg on their box? Takes only a minute. Does running python -c 'import psycopg' die? |
|
Back to top |
|
|
Ulot n00b
Joined: 26 Apr 2002 Posts: 39
|
Posted: Thu Jun 05, 2003 6:12 pm Post subject: |
|
|
I'll try it out when I get to the machine again, but that won't be for a day or two. |
|
Back to top |
|
|
2thumbs n00b
Joined: 04 Jun 2003 Posts: 6 Location: Edmonton, AB Canada
|
Posted: Thu Jun 05, 2003 7:31 pm Post subject: |
|
|
That would be helpful. I put Debian 3.0 onto the other partition ( blasphemy ) and psycopg 1.1.4 works great on there. Although the version of postgresql I used is older (7.2 vs 7.3), I don't think that's the problem |
|
Back to top |
|
|
Weeve Retired Dev
Joined: 30 Oct 2002 Posts: 641
|
Posted: Fri Jun 06, 2003 10:58 am Post subject: |
|
|
Running python -c 'import psycopg' appears works for me. The command executes and returns an exit code of 0 |
|
Back to top |
|
|
2thumbs n00b
Joined: 04 Jun 2003 Posts: 6 Location: Edmonton, AB Canada
|
Posted: Fri Jun 06, 2003 8:03 pm Post subject: |
|
|
Completely bizare. Running emerge psycopg builds and installs version 1.0.1. That doesn't work. Building any version against the emerged python 2.1/postgresql 7.3/egenix mx base fails. Installing my own versions of python, postgres, egenix, and building against that fails. Building it on the same machine running Debian/testing, with the same versions of the tools works. |
|
Back to top |
|
|
greenbob n00b
Joined: 24 Jun 2003 Posts: 48 Location: Charlotte, NC
|
Posted: Sat Jun 09, 2007 8:31 am Post subject: |
|
|
I had an issue after I upgraded python, even after running 'python-updater'
I re-emerged libpq and I believe that fixed the issue. _________________ "A single death is a tragedy, a million deaths is a statistic." -Joseph Stalin |
|
Back to top |
|
|
|