Re: Python compile issue?

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

    This is more likely to be a stdint.h issue.  If Python thinks it is
    compiling under FreeBSD-4.x it is probably trying to redefine stdin
    types that, in fact, exist in DragonFly.

    Search the distribution for where PyInt_Type is defined.  If you can't
    track it down I or one of the other developers will try to find it.

					-Matt
					Matthew Dillon 
					<dillon@xxxxxxxxxxxxx>


:I am having problems building Python 2.3.3 from the source tarball on 
:-CURRENT whereas Python built without problems a few months ago.
:
:Most of it compiles OK with the exception of certain "extensions" (eg. 
:struct, regex etc)
:
:Typically I get
:
:[..snip..]
:building 'struct' extension
:ld build/temp.dragonfly-1.0-CURRENT-i386-2.3/structmodule.o 
:-L/usr/local/lib -o build/lib.dragonfly-1.0-CURRENT-i386-2.3/struct.so
:/usr/libexec/gcc2/elf/ld: warning: cannot find entry symbol _start; 
:defaulting to 08048074
:build/temp.dragonfly-1.0-CURRENT-i386-2.3/structmodule.o: In function 
:`get_pylong':
:/usr/home/steve/othersrc/python/Python-2.3.3/Modules/structmodule.c:90: 
:undefined reference to `PyInt_Type'
:
:<wild guess>
:Maybe this is a linker problem related to the recent GCC changes?
:</wild guess>
:
:-- Steve