Description of problem:
smart's detection on python build parameters, most notably HAVE_MEMMOVE, is
broken on FC6 (see bug #201434).

Version-Release number of selected component (if applicable):
smart-0.42-xxx

How reproducible:
always

Steps to Reproduce:
1.Try to build the package
2.
3.
  
Actual results:
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4
-m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -D_GNU
_SOURCE -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic
-fasynchronous-unwind-tables -fPIC -DXML_STATIC -DXML_NS=1 -DXML
_DTD=1 -DXML_CONTEXT_BYTES=1024 -DBYTEORDER=1234 -Ismart/util/celementtree/expat
-I/usr/include/python2.4 -c smart/util/celementtree/expat/xmlparse.c -o
build/temp.linux-i686-2.4/smart/util/celementtree/expat/x
mlparse.o
smart/util/celementtree/expat/xmlparse.c:75:2: error: #error memmove does not
exist on this platform, nor is a substitute available


Expected results:
Should contain -DHAVE_MEMMOVE

Additional info:
Self-submitting to keep a tracking bug and a dependency to bug #201434. Also for
having a reference point when it comes to failed rebuild in new chroots or for
mass-rebuilds for FC6.