Re: Python 2.4a compatibility patches

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

    This brings up a very good point, and that is what to do
    with the __FreeBSD__ defines.

    It seems to me that we have an excellent opportunity here
    with both gcc2 and gcc3 in the tree, and that is to remove
    __FreeBSD__ from gcc3 builds.  This would allow people to
    test with or without __FreeBSD__ by using gcc2 or gcc3
    (a simple setenv CCVER gccX environment variable).

    I am not going to do it this instant, but I will do it
    next weekend when I clean up contrib/gcc3.

					-Matt
					Matthew Dillon 
					<dillon@xxxxxxxxxxxxx>

:A lot of the patches simply add '|| defined(__DragonFly__)' to the
:FreeBSD conditionals in anticipation of the day when DragonFly no
:longer masquerades as FreeBSD.  The most useful parts of the patch are
:the 'configure' changes and the test suite support.
:
:Nothing miraculaous, but it works for me:
:
:    http://www.indelible.org/dragonfly/python/
:
:Note that this will fix the 'PyInt_Type not defined' build errors that
:were reported on one of the DragonFly lists not too long ago.  I've
:lost my reference to that original message, though.
:
:I'll submit this stuff back to the Python project soon.
:
:-- 
:Jon Parise (jon@xxxxxxxxxxxxx)  ::  "Scientia est Potentia"