KDE 3.5 doesn't want to compile. karamba_python.cpp errors galore

[resonant evil]

Hi everyone..  I just installed a minimal 7.0-CURRENT install and was
recently compiling everything.. I successfully compiled xorg and what
not, but now when I am trying to do a 'make install' in
/usr/ports/x11/kde3, like 3 hours into the compilation process I'm
getting a boatload of errors that are stopping me from continuing..  I
sadly do not have a bloody clue how to fix it; I don't know Python or
C..  So hopefully you pros can help me out :-)

Here is the output that is stopping the show:

gmake[3]: Entering directory `/usr/ports/misc/kdeutils3/work/kdeutils-3.5.0/supe
rkaramba/src'
if c++ -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/local/include -I/usr/X11R6/include
  -I/usr/local/include  -I/usr/local/include/python2.4  -D_THREAD_SAFE -pthread
-DQT_THREAD_SUPPORT   -I/usr/local/include -I/usr/local/include  -I/usr/X11R6/in
clude -D_GETOPT_H -D_THREAD_SAFE   -Wno-long-long -Wundef -Wall -W -Wpointer-ari
th -DNDEBUG -DNO_DEBUG -O2 -O2 -fno-strict-aliasing -pipe -Wno-non-virtual-dtor
-fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CA
ST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION  -MT karamba_python.o -MD -MP
-MF ".deps/karamba_python.Tpo" -c -o karamba_python.o karamba_python.cpp; \
then mv -f ".deps/karamba_python.Tpo" ".deps/karamba_python.Po"; else rm -f ".de
ps/karamba_python.Tpo"; exit 1; fi
karamba_python.cpp: In static member function `static void KarambaPython::initPy
thon()':
karamba_python.cpp:370: error: `PyEval_InitThreads' undeclared (first use this f
unction)
karamba_python.cpp:370: error: (Each undeclared identifier is reported only once
 for each function it appears in.)
karamba_python.cpp:376: error: `PyEval_ReleaseLock' undeclared (first use this f
unction)
karamba_python.cpp: In static member function `static void KarambaPython::shutdo
wnPython()':
karamba_python.cpp:386: error: `PyEval_AcquireLock' undeclared (first use this f
unction)
karamba_python.cpp: In member function `void KarambaPython::getLock(PyThreadStat
e**)':
karamba_python.cpp:393: error: `PyEval_AcquireLock' undeclared (first
use this function)
karamba_python.cpp: In member function `void KarambaPython::releaseLock(PyThread
State*)':
karamba_python.cpp:409: error: `PyEval_ReleaseLock' undeclared (first use this f
unction)
gmake[3]: *** [karamba_python.o] Error 1
gmake[3]: Leaving directory `/usr/ports/misc/kdeutils3/work/kdeutils-3.5.0/super
karamba/src'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory
`/usr/ports/misc/kdeutils3/work/kdeutils-3.5.0/superkaramba'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/misc/kdeutils3/work/kdeutils-3.5.0'
gmake: *** [all] Error 2
*** Error code 2

Stop in /usr/ports/misc/kdeutils3.
*** Error code 1

Stop in /usr/ports/x11/kde3.
bash-2.05b#


*** SORRY if this looks or pasted like crap, I'm trying to manage
through gmail here in bloody lynx from a console and do all my cutting
and pasting as well.

I always ask on #FreeBSD on irc.freenode.net before I visit the
mailing lists for help, but all they can tell me in there is that the
problem looks like "sloppy code" or "unrefined code" (Don't hold me to
this!  I know squat about coding!)
They did all tell me though that this looks like a pretty serious
problem and should be reported to the lists, so hopefully somebody
here can give me some insight!  I know compiling from scratch isn't
always reccomended, and the easiest way is to install everything right
at installtime, but I was on a very short schedule and have been
having to do things in small sections each day, which is why I did the
'minimal' install and am just trying to choose what I want..  I also
know that 7.0-CURRENT is considered unstable and isn't reccomended for
usage, but I need to make use of multiple experimental Atheros patches
for my 6th generation ath card that has NO native support yet.  (I've
already done an entire rebuild world process without problems)

Hopefully somebody can help me with resolving this problem, I look
forward to a response

Thank you in advance everyone :)
-Ryan