Thanks soulfire for your suggestion. Meanwhile I found some time to dig into the code as well. Anyway, I added the base in the list of valid toolkit-options, thus you can call configure with the argument --with-toolkit=base, and everyting works as it used to be. Here the diff:
diff -Naur amule-cvs.orig/configure amule-cvs/configure
--- amule-cvs.orig/configure 2007-09-13 06:01:13.000000000 +0100
+++ amule-cvs/configure 2007-09-13 20:05:12.714543250 +0100
@@ -7368,12 +7368,13 @@
if test "$TOOLKIT" != "gtk1" -a "$TOOLKIT" != "gtk2" -a \
"$TOOLKIT" != "msw" -a "$TOOLKIT" != "motif" -a \
"$TOOLKIT" != "x11" -a "$TOOLKIT" != "mac" -a \
- "$TOOLKIT" != "mgl" -a "$TOOLKIT" != "dfb" ; then
+ "$TOOLKIT" != "mgl" -a "$TOOLKIT" != "dfb" -a \
+ "$TOOLKIT" != "base" ; then
{ { echo "$as_me:$LINENO: error:
- Unrecognized option value (allowed values: auto, gtk1, gtk2, msw, motif, x11, mac, mgl, dfb)
+ Unrecognized option value (allowed values: auto, gtk1, gtk2, msw, motif, x11, mac, mgl, dfb, base)
" >&5
echo "$as_me: error:
- Unrecognized option value (allowed values: auto, gtk1, gtk2, msw, motif, x11, mac, mgl, dfb)
+ Unrecognized option value (allowed values: auto, gtk1, gtk2, msw, motif, x11, mac, mgl, dfb, base)
" >&2;}
{ (exit 1); exit 1; }; }
fi
Could any of the official developers have look at the patch, please?