freeBSD 2.1.1 extension problem

Andrew MacIntyre andymac at bullseye.apana.org.au
Tue Aug 28 12:19:00 CEST 2001


On Mon, 27 Aug 2001, Robin Becker wrote:

> In article <WWVECJAoEii7Ewnx at jessikat.fsnet.co.uk>, Robin Becker <robin at jessikat.fsnet.co.uk>
> writes

{...}

> >I'm guessing this might be some difference in the way the two
> >pythons/distutils were configured.
>
>
> Further research says that wchar.h was added to ISO C90 with amendment 1.
>
> Also it seems that
> http://docs.freebsd.org/mail/archive/2001/freebsd-i18n/20010520.freebsd-i18n.html
> mentions wchar.h a lot beginning 2001/may so perhaps Python-2.1.1 package
> has the requirement for wchar.h built in because freeBSD recently added
> wchar.h.
>
> Looking in the two config.h fiels, I see one with #define HAVE_WCHAR_H 1
> and one without.

If the binary Python package you've installed was built on a newer FreeBSD
(which seems likely from what I've gleaned from your posts) this is not
surprising, as the configure script would have found the errant header on
the newer system.

--
Andrew I MacIntyre                     "These thoughts are mine alone..."
E-mail: andymac at bullseye.apana.org.au  | Snail: PO Box 370
        andymac at pcug.org.au            |        Belconnen  ACT  2616
Web:    http://www.andymac.org/        |        Australia





More information about the Python-list mailing list