Apache OpenOffice (AOO) Bugzilla – Issue 25451
blindly assumes GNU make == gmake
Last modified: 2009-01-07 12:38:18 UTC
Hi, makefile.mk in libjpeg/ blindly assumes that GNU make is gmake. This fails: ============= Building project libjpeg ============= /home/rene/OpenOffice.org/Source/cws_src680_ooo20040225/libjpeg ------------- mkdir ./unxlngi4.pro/misc/build/jpeg-6b/ mkdir: cannot create directory `./unxlngi4.pro/misc/build/jpeg-6b/': File existscd ./unxlngi4.pro/misc/build/jpeg-6b/ && gmake install && touch so_built_libjpeg gmake: Command not found. dmake: Error code 1, while making './unxlngi4.pro/misc/build/so_built_libjpeg' ---* TG_SLO.MK *--- ERROR: Error 65280 occurred while making /home/rene/OpenOffice.org/Source/cws_src680_ooo20040225/libjpeg dmake: Error code 1, while making 'build_all' ---* TG_SLO.MK *--- rene@zero:~/OpenOffice.org/Source/cws_src680_ooo20040225$ rene@zero:~/OpenOffice.org/Source/cws_src680_ooo20040225$ gmake -v bash: gmake: command not found rene@zero:~/OpenOffice.org/Source/cws_src680_ooo20040225$ make -v GNU Make 3.80 GNU make is installed under GNU based systems as just 'make' - without gmake alias. Regards, René
ah, btw, I am not sure that framework is richt but I didn't find an other component to better fit it in. Reassign as necessary :-)
TM->SVesik: Please have a look.
same problem building gtk in cws_src680_ooo20040329 jim@sun:~/680/gtk$ build build -- version: 1.99 Checking dmake... Using version 4.10 /home/jim/680/gtk/pkgconfig ------------- /home/jim/680/gtk/glib ------------- mkdir ../unxlngs.pro/misc/build/glib-2.2.3/ mkdir: cannot create directory `../unxlngs.pro/misc/build/glib-2.2.3/': File exists cd ../unxlngs.pro/misc/build/glib-2.2.3/ && gmake install && touch so_built_glib gmake: Command not found. dmake: Error code 1, while making '../unxlngs.pro/misc/build/so_built_glib' ---* TG_SLO.MK *--- ERROR: Error 65280 occurred while making /home/jim/680/gtk/glib jim@sun:~/680/gtk$
In LinuxSparcEnv.Set:setenv GNUMAKE "make" is set by configure, i suppose it is only for making dmake but it could be used anywhere? Somehow the other external modules know how to make themselves? It is no solution but just for an experiment, these modules build OK if I make a link gmake-->make
is this still an open issue ?
mh: > is this still an open issue ? no, I think we can close it.
.