Re: Re: PHP 4.2.3 release process

At 15:08 7/25/2002 +0200, Sascha Schumann wrote:

With buildconf you get the error in build/build2.mk, cause buildconf has the same issue.

    Is it so hard to simply accept that you need to type "make"
    instead of "gmake" or "unset MAKE" when building PHP?

In my case - yes. Since that involves, resetting my path also, which then will use other old tools as well. Ok - maybe it's me just being lazy, but why not let the puter fix it, that's what they're for, right? :-) Below is the patch I use - it's ugly, but works always. --- configure.in.dist Wed Apr 3 21:22:12 2002

+++ configure.in        Wed Apr  3 21:22:46 2002

@@ -94,7 +94,10 @@ *darwin*|*rhapsody*)

     CPPFLAGS="$CPPFLAGS -traditional-cpp";;

*bsdi*)

-    BSD_MAKEFILE=yes;;
+    if test "GNU" != ${MAKE} --version | sed -n -e "s|^GNU.*|GNU|p"; then
+        BSD_MAKEFILE=yes
+    fi
+    ;;

*beos*)

     beos_threads=1
     LIBS="$LIBS -lbe -lroot";;
--- buildconf.dist      Tue Sep 26 13:19:38 2000

+++ buildconf Wed Mar 27 19:43:31 2002 @@ -30,7 +30,10 @@ case "uname" in *BSD/OS*)

-    ./build/bsd_makefile;;
+    if test "GNU" != ${MAKE} --version | sed -n -e "s|^GNU.*|GNU|p"; then
+        ./build/bsd_makefile
+    fi
+    ;;

esac ${MAKE:-make} -s -f build/build.mk AMFLAGS="$automake_flags" Met vriendelijke groeten / With kind regards, Webmaster IDG.nl Melvyn Sopacua <@Logan> I spent a minute looking at my own code by accident. <@Logan> I was thinking "What the hell is this guy doing?" http://www.geekissues.org/quotes/top50.html?6824