patch for python configure for freeBSD and Zope
Hi, I'm using freeBSD 4.2-RELEASE and just tried to install python-1.5.2 and Zope. If you are trying to do the same and tun into the following error when trying to start zope, then apply this patch to the configure script of python and rebuild it. ImportError: ./ExtensionClass.so: Undefined symbol "PyMethod_Type" have fun Matt
Hi, I'm using freeBSD 4.2-RELEASE and just tried to install python-1.5.2 and Zope. If you are trying to do the same and tun into the following error when trying to start zope, then apply this patch to the configure script of python and rebuild it.
ImportError: ./ExtensionClass.so: Undefined symbol "PyMethod_Type"
Matt, Is this an error in the port itself of python? Python 2.0 is in ports as well as zope. If there is a problem with either port can you give more detail so the apropriate maintainer can be notified. Thanks! -- ============================================================================= -Chris Watson (316) 326-3862 | FreeBSD Consultant, FreeBSD Geek Work: scanner@jurai.net | Open Systems Inc., Wellington, Kansas Home: scanner@deceptively.shady.org | http://open-systems.net ============================================================================= WINDOWS: "Where do you want to go today?" LINUX: "Where do you want to go tomorrow?" BSD: "Are you guys coming or what?" ============================================================================= GNU = Gnu's Non-portable & Unstable irc.openprojects.net #FreeBSD -Join the revolution! ICQ: 20016186
On Mon, 22 Jan 2001, Chris Watson wrote:
Hi, I'm using freeBSD 4.2-RELEASE and just tried to install python-1.5.2 and Zope. If you are trying to do the same and tun into the following error when trying to start zope, then apply this patch to the configure script of python and rebuild it.
ImportError: ./ExtensionClass.so: Undefined symbol "PyMethod_Type"
Matt,
Is this an error in the port itself of python? Python 2.0 is in ports as well as zope. If there is a problem with either port can you give more detail so the apropriate maintainer can be notified. Thanks!
Sorry, to be more explicit : I built python 1.5.2 and Zope 2.2.2 from source, although the most recent stable release of Zope also gave the same error. I did not use the ports distribution of python or zope, so I don't know if the same default configure script is used by them too. Is that what you wanted to know? Matt
-- ============================================================================= -Chris Watson (316) 326-3862 | FreeBSD Consultant, FreeBSD Geek Work: scanner@jurai.net | Open Systems Inc., Wellington, Kansas Home: scanner@deceptively.shady.org | http://open-systems.net ============================================================================= WINDOWS: "Where do you want to go today?" LINUX: "Where do you want to go tomorrow?" BSD: "Are you guys coming or what?" ============================================================================= GNU = Gnu's Non-portable & Unstable irc.openprojects.net #FreeBSD -Join the revolution! ICQ: 20016186
--
Sorry, to be more explicit : I built python 1.5.2 and Zope 2.2.2 from source, although the most recent stable release of Zope also gave the same error.
I did not use the ports distribution of python or zope, so I don't know if the same default configure script is used by them too.
Is that what you wanted to know?
Yes. That answers what I wanted to know. Is there a specific reason you didnt want to use the ports? Since the ports work just fine im assuming there is. I would like to know if its because the ports are lacking a feature you need so they can be fixed? If not why not just use the ports? -- ============================================================================= -Chris Watson (316) 326-3862 | FreeBSD Consultant, FreeBSD Geek Work: scanner@jurai.net | Open Systems Inc., Wellington, Kansas Home: scanner@deceptively.shady.org | http://open-systems.net ============================================================================= WINDOWS: "Where do you want to go today?" LINUX: "Where do you want to go tomorrow?" BSD: "Are you guys coming or what?" ============================================================================= GNU = Gnu's Non-portable & Unstable irc.openprojects.net #FreeBSD -Join the revolution! ICQ: 20016186
On Mon, 22 Jan 2001, Chris Watson wrote:
Sorry, to be more explicit : I built python 1.5.2 and Zope 2.2.2 from source, although the most recent stable release of Zope also gave the same error.
I did not use the ports distribution of python or zope, so I don't know if the same default configure script is used by them too.
Is that what you wanted to know?
Yes. That answers what I wanted to know. Is there a specific reason you didnt want to use the ports? Since the ports work just fine im assuming there is. I would like to know if its because the ports are lacking a feature you need so they can be fixed? If not why not just use the ports?
No reason except that I have an install script for python, zope, and modules (including configuration) for both that I "know" form a stable environment on our production servers, whether linux, or freeBSD. I should try the ports distribution and run my unit tests to perhaps build a more likely to be stable freeBSD installer for our work. Matt
-- ============================================================================= -Chris Watson (316) 326-3862 | FreeBSD Consultant, FreeBSD Geek Work: scanner@jurai.net | Open Systems Inc., Wellington, Kansas Home: scanner@deceptively.shady.org | http://open-systems.net ============================================================================= WINDOWS: "Where do you want to go today?" LINUX: "Where do you want to go tomorrow?" BSD: "Are you guys coming or what?" ============================================================================= GNU = Gnu's Non-portable & Unstable irc.openprojects.net #FreeBSD -Join the revolution! ICQ: 20016186
No reason except that I have an install script for python, zope, and modules (including configuration) for both that I "know" form a stable environment on our production servers, whether linux, or freeBSD. I should try the ports distribution and run my unit tests to perhaps build a more likely to be stable freeBSD installer for our work.
That would be a good idea. Try that and let me know if your tests work. People go to alot of trouble to make a port. It makes little sense to re-invent the wheel especially with ports. If your tests fail let me know where and how and I will see about getting the maintainer of the offending port to ensure it works with your tests and application. -- ============================================================================= -Chris Watson (316) 326-3862 | FreeBSD Consultant, FreeBSD Geek Work: scanner@jurai.net | Open Systems Inc., Wellington, Kansas Home: scanner@deceptively.shady.org | http://open-systems.net ============================================================================= WINDOWS: "Where do you want to go today?" LINUX: "Where do you want to go tomorrow?" BSD: "Are you guys coming or what?" ============================================================================= GNU = Gnu's Non-portable & Unstable irc.openprojects.net #FreeBSD -Join the revolution! ICQ: 20016186
participants (2)
-
Chris Watson -
matt