Davide Ferrari <[EMAIL PROTECTED]> writes: > devel lms-kit-builder # gmake > gmake -C carob- CUSTOM=libmysequoia # comment out CUSTOM here to let carob > subdir decide > gmake[1]: Entering directory `/root/carob_cvs/carob' > gmake[1]: Nothing to be done for `all'. > gmake[1]: Leaving directory `/root/carob_cvs/carob' > ./lmsbuild.sh > + [ -e ./build.properties ] > + pwd > + CAROBPATH=/root/carob_cvs/lms-kit-builder/carob- > + cd libmysequoia- > + OSCPPFLAGS=-I/usr/local/include > + OSLDFLAGS=-L/usr/local/lib -L/usr/local/lib/mysql > + test -e ./config.status > + ./configure CAROBDIR=/root/carob_cvs/lms-kit-builder/carob- > CONFIG_SITE=main.config.site > ./lmsbuild.sh: ./configure: not found > gmake: *** [build] Error 127
Ok you got me: "gmake dev" is a hack for developers. Future, non-CVS kits will be distributed WITH a ./configure script. Meanwhile, use the libmysequoia/autogen.sh script to generate a libmysequoia/configure script and related files. The autogen.sh script needs some adjustments for FreeBSD, check comments inside. Don't worry if autogen.sh fails at the end: as long as it gives you a libmysequoia/configure script you are good and can start over from lms-kit-builder. Thanks again for beta-testing this "in real time". _______________________________________________ Carob mailing list [email protected] https://forge.continuent.org/mailman/listinfo/carob
