Date: Mon, 27 Aug 2001 21:30:35 -0500 From: Mike Meyer <mwm@mired.org> To: Robin Becker <robin@jessikat.fsnet.co.uk> Cc: questions@freebsd.org Subject: Re: Python-2.1.1 extension problem Message-ID: <15243.587.29088.614156@guru.mired.org> In-Reply-To: <46650695@toto.iv>
next in thread | previous in thread | raw e-mail | index | archive | help
Robin Becker <robin@jessikat.fsnet.co.uk> types: > Whilst trying to recompile an extension with freeBSD 4.2 + Python-2.1.1 > I'm getting the following error. It would be nice if we new what the extension was. > /usr/local/include/python2.1/unicodeobject.h:91: wchar.h: No such file > or directory > > This extension compiled OK with Python-2.1. > So must I upgrade my OS or is this a buglet of some kind? Well it doesn' wasn't a wchar.h in 4.2-RELEASE. Or 4.3-RELEASE, for that matter. However, Python's config should notice that it's missing and build appropriately. > This is a bit stranger than I thought. On one system running freebsd- > 4.1.1-STABLE I have to build my own Python-2.1.1 as it's a colo machine. > On that system I can build the extension fine. Certainly doesn't seem to > have a wchar.h though. > > On the problem system freebsd-4.2-STABLE with the recently upgraded > binary packaged Python-2.1.1 I am unable to build the package. There's the answer. The binary package of Python-2.1.1 was probably built on a system that had a wchar.h. You should be able to build Python-2.1.1 from the port and use that. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15243.587.29088.614156>