Problem w/ Python 2.3.5

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Problem w/ Python 2.3.5

Toni Mueller-7
Hi,

finally, I broke down and installed some X11 stuff on a server in the
hope to gain PIL there... but first, I need to rebuild Python (re-run
after the same breakage):


hostname 11:42:23 /home/obsd/ports/lang/python/2.3
# /usr/bin/make package
===>  Building for python-2.3.5p2
case $MAKEFLAGS in  *-s*)  CC='cc -pthread' LDSHARED='cc -pthread -shared -fPIC -L/home/obsd/ports/lang/python/2.3/w-python-2.3.5p2/Python-2.3.5' OPT='-DNDEBUG -O2 -pipe  -DTHREAD_STACK_SIZE=0x180000 -fPIC' ./python -E /home/obsd/ports/lang/python/2.3/w-python-2.3.5p2/Python-2.3.5/setup.py -q build;;  *)  CC='cc -pthread' LDSHARED='cc -pthread -shared -fPIC -L/home/obsd/ports/lang/python/2.3/w-python-2.3.5p2/Python-2.3.5' OPT='-DNDEBUG -O2 -pipe  -DTHREAD_STACK_SIZE=0x180000 -fPIC' ./python -E /home/obsd/ports/lang/python/2.3/w-python-2.3.5p2/Python-2.3.5/setup.py build;;  esac
running build
running build_ext
*** Error code 4

Stop in /home/obsd/ports/lang/python/2.3/w-python-2.3.5p2/Python-2.3.5 (line 340 of Makefile).
*** Error code 1

Stop in /home/obsd/ports/lang/python/2.3 (line 1807 of /home/obsd/ports/infrastructure/mk/bsd.port.mk).



I've made sure to have only OPENBSD_3_8 tagged stuff on that box.


Any ideas?


Best,
--Toni++

Reply | Threaded
Open this post in threaded view
|

Re: Problem w/ Python 2.3.5

Joachim Schipper
On Tue, Jan 17, 2006 at 11:56:38AM +0100, Toni Mueller wrote:

> Hi,
>
> finally, I broke down and installed some X11 stuff on a server in the
> hope to gain PIL there... but first, I need to rebuild Python (re-run
> after the same breakage):
>
>
> hostname 11:42:23 /home/obsd/ports/lang/python/2.3
> # /usr/bin/make package
> ===>  Building for python-2.3.5p2
> case $MAKEFLAGS in  *-s*)  CC='cc -pthread' LDSHARED='cc -pthread -shared -fPIC -L/home/obsd/ports/lang/python/2.3/w-python-2.3.5p2/Python-2.3.5' OPT='-DNDEBUG -O2 -pipe  -DTHREAD_STACK_SIZE=0x180000 -fPIC' ./python -E /home/obsd/ports/lang/python/2.3/w-python-2.3.5p2/Python-2.3.5/setup.py -q build;;  *)  CC='cc -pthread' LDSHARED='cc -pthread -shared -fPIC -L/home/obsd/ports/lang/python/2.3/w-python-2.3.5p2/Python-2.3.5' OPT='-DNDEBUG -O2 -pipe  -DTHREAD_STACK_SIZE=0x180000 -fPIC' ./python -E /home/obsd/ports/lang/python/2.3/w-python-2.3.5p2/Python-2.3.5/setup.py build;;  esac
> running build
> running build_ext
> *** Error code 4
>
> Stop in /home/obsd/ports/lang/python/2.3/w-python-2.3.5p2/Python-2.3.5 (line 340 of Makefile).
> *** Error code 1
>
> Stop in /home/obsd/ports/lang/python/2.3 (line 1807 of /home/obsd/ports/infrastructure/mk/bsd.port.mk).
>
>
>
> I've made sure to have only OPENBSD_3_8 tagged stuff on that box.

Not reproducible on my system (3.8-stable/i386) - python-2.3.5p2 builds
fine. (Do note that this is under /usr/ports, and as root.)

Try to find a more detailed error log. Are you certain your hardware
works as expected?

                Joachim

Reply | Threaded
Open this post in threaded view
|

Re: Problem w/ Python 2.3.5

Toni Mueller-7

Hi Joachim,

On Tue, 17.01.2006 at 17:00:24 +0100, Joachim Schipper <[hidden email]> wrote:
> On Tue, Jan 17, 2006 at 11:56:38AM +0100, Toni Mueller wrote:
> > case $MAKEFLAGS in  *-s*)  CC='cc -pthread' LDSHARED='cc -pthread -shared -fPIC -L/home/obsd/ports/lang/python/2.3/w-python-2.3.5p2/Python-2.3.5' OPT='-DNDEBUG -O2 -pipe  -DTHREAD_STACK_SIZE=0x180000 -fPIC' ./python -E /home/obsd/ports/lang/python/2.3/w-python-2.3.5p2/Python-2.3.5/setup.py -q build;;  *)  CC='cc -pthread' LDSHARED='cc -pthread -shared -fPIC -L/home/obsd/ports/lang/python/2.3/w-python-2.3.5p2/Python-2.3.5' OPT='-DNDEBUG -O2 -pipe  -DTHREAD_STACK_SIZE=0x180000 -fPIC' ./python -E /home/obsd/ports/lang/python/2.3/w-python-2.3.5p2/Python-2.3.5/setup.py build;;  esac
> > running build
> > running build_ext
> > *** Error code 4

> Not reproducible on my system (3.8-stable/i386) - python-2.3.5p2 builds
> fine. (Do note that this is under /usr/ports, and as root.)

thanks for your message. In the meantime, I think I found out that this
means "interrupted system call", and no, I don't have any better error
messages.

> Try to find a more detailed error log. Are you certain your hardware
> works as expected?

Well... that's what I'm not sure about right now, too. The box is
otherwise mostly idle, and has been reliable except for this problem
now. Any ideas on how to check it?


Best,
--Toni++

Reply | Threaded
Open this post in threaded view
|

Re: Problem w/ Python 2.3.5

Joachim Schipper
On Tue, Jan 17, 2006 at 10:25:55PM +0100, Toni Mueller wrote:

>
> Hi Joachim,
>
> On Tue, 17.01.2006 at 17:00:24 +0100, Joachim Schipper <[hidden email]> wrote:
> > On Tue, Jan 17, 2006 at 11:56:38AM +0100, Toni Mueller wrote:
> > > case $MAKEFLAGS in  *-s*)  CC='cc -pthread' LDSHARED='cc -pthread -shared -fPIC -L/home/obsd/ports/lang/python/2.3/w-python-2.3.5p2/Python-2.3.5' OPT='-DNDEBUG -O2 -pipe  -DTHREAD_STACK_SIZE=0x180000 -fPIC' ./python -E /home/obsd/ports/lang/python/2.3/w-python-2.3.5p2/Python-2.3.5/setup.py -q build;;  *)  CC='cc -pthread' LDSHARED='cc -pthread -shared -fPIC -L/home/obsd/ports/lang/python/2.3/w-python-2.3.5p2/Python-2.3.5' OPT='-DNDEBUG -O2 -pipe  -DTHREAD_STACK_SIZE=0x180000 -fPIC' ./python -E /home/obsd/ports/lang/python/2.3/w-python-2.3.5p2/Python-2.3.5/setup.py build;;  esac
> > > running build
> > > running build_ext
> > > *** Error code 4
>
> > Not reproducible on my system (3.8-stable/i386) - python-2.3.5p2 builds
> > fine. (Do note that this is under /usr/ports, and as root.)
>
> thanks for your message. In the meantime, I think I found out that this
> means "interrupted system call", and no, I don't have any better error
> messages.

Hmmm... is this crash reproducible on your box? If so, you might want to
use ktrace. It will give you gobs of data, but is likely to also tell
you exactly what syscall was interrupted, which is likely to give you a
hint.

You'll want to either snip very carefully or host the file someplace; if
neither is possible, you can send it to me via private mail, but keeping
it on the list is more likely to yield sensible results.

> > Try to find a more detailed error log. Are you certain your hardware
> > works as expected?
>
> Well... that's what I'm not sure about right now, too. The box is
> otherwise mostly idle, and has been reliable except for this problem
> now. Any ideas on how to check it?

If it's memory, it's likely to be found by memtest86, if your hardware
is i386. It can be had from various sources, and is included on the
Knoppix CD, which I can recommend - it's not OpenBSD, but occasionally
very useful.

                Joachim

Reply | Threaded
Open this post in threaded view
|

Re: Problem w/ Python 2.3.5

steven mestdagh
In reply to this post by Toni Mueller-7
On Tue, Jan 17, 2006 at 11:56:38AM +0100, Toni Mueller wrote:
> Hi,
>
> finally, I broke down and installed some X11 stuff on a server in the
> hope to gain PIL there... but first, I need to rebuild Python (re-run
> after the same breakage):

with PIL you are referring to the python imaging library, right?
this is available as a package (py-Imaging).
is there a reason why you cannot use packages?

"broke down and installed some X11 stuff" sounds pretty vague.

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

Reply | Threaded
Open this post in threaded view
|

Re: Problem w/ Python 2.3.5

Dave Mangot
In reply to this post by Joachim Schipper
Joachim Schipper ([hidden email]) shaped the electrons to say:
>
> If it's memory, it's likely to be found by memtest86, if your hardware
> is i386. It can be had from various sources, and is included on the
> Knoppix CD, which I can recommend - it's not OpenBSD, but occasionally
> very useful.

www.Memtest86.com also offers bootable ISOs.  No Knoppix required.

                        -Dave
--


"'Crazy' loves company too." - Peggy (1/23/05)

Reply | Threaded
Open this post in threaded view
|

Re: Problem w/ Python 2.3.5

Toni Mueller-7
In reply to this post by steven mestdagh


Hello Steve,

On Wed, 18.01.2006 at 06:38:25 +0100, steven mestdagh <[hidden email]> wrote:
> with PIL you are referring to the python imaging library, right?
> this is available as a package (py-Imaging).
> is there a reason why you cannot use packages?

yes, the reason is that I need Plone 2.1.1 which in turn requires PIL
1.1.5, not 1.1.4 which is in ports. In most cases, when the updated
package is mostly reflected in new version numbers in the Makefile, and
a new distinfo, this is not a problem.

> "broke down and installed some X11 stuff" sounds pretty vague.

By this I meant that I installed the xbase38.tgz, xetc38.tgz and
xshare38.tgz which I normally don't install. Unfortunately, the PIL port
can't easily be built w/o tk which in turn requires X11.


Best,
--Toni++

Reply | Threaded
Open this post in threaded view
|

Re: Problem w/ Python 2.3.5

steven mestdagh
On Mon, Jan 23, 2006 at 11:22:28AM +0100, Toni Mueller wrote:

>
>
> Hello Steve,
>
> On Wed, 18.01.2006 at 06:38:25 +0100, steven mestdagh <[hidden email]> wrote:
> > with PIL you are referring to the python imaging library, right?
> > this is available as a package (py-Imaging).
> > is there a reason why you cannot use packages?
>
> yes, the reason is that I need Plone 2.1.1 which in turn requires PIL
> 1.1.5, not 1.1.4 which is in ports. In most cases, when the updated
> package is mostly reflected in new version numbers in the Makefile, and
> a new distinfo, this is not a problem.
>
> > "broke down and installed some X11 stuff" sounds pretty vague.
>
> By this I meant that I installed the xbase38.tgz, xetc38.tgz and
> xshare38.tgz which I normally don't install. Unfortunately, the PIL port
> can't easily be built w/o tk which in turn requires X11.

did you use ldconfig to add /usr/X11R6/lib? this should be done
automatically by rc(8) on reboot.

anyway, this is not really supported. you could consider -current which
has both PIL 1.1.5 and plone 2.1.1.

steven

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm