From: Hoehle, Joerg-C. <Joe...@t-...> - 2003-04-01 14:06:36
|
Hi, I have the feeling that CLISP's Makefile does a little too much = auto/cyclic-magic/detection/regeneration or whatever. This seems to = cause -n to become useless. How comes that make -n reports lots of things to be done, when the = actual make eventually does next to nothing? build-gcc> make lisp.run =20 sh config.status --header=3Dunixconf.h =20 config.status: creating unixconf.h =20 config.status: unixconf.h is unchanged compare with build-gcc> make -n lisp.run = =20 sh config.status --header=3Dunixconf.h = =20 gcc -I/home/hoehle/include -W -Wswitch -Wcomment -Wpointer-arith = -Wimplicit -Wreturn-type -fomit-frame-pointer -Wno-sign-compare -O2 -fexpensive-optimizations = -DUNICODE -DDYNAMI C_FFI -DDYNAMIC_MODULES -x none genclisph.o -o genclisph = =20 (echo '#ifndef _CLISP_H' ; echo '#define _CLISP_H' ; echo ; grep '^#' = unixconf.h ; echo ; grep '^#' intparam.h ; echo ; ./genclisph ; echo ; echo '#endif /* = _CLISP_H */') > clisp .h = =20 rm -f genclisph = =20 gcc -I/home/hoehle/include -W -Wswitch -Wcomment -Wpointer-arith = -Wimplicit -Wreturn-type -fomit-frame-pointer -Wno-sign-compare -O2 -fexpensive-optimizations = -DUNICODE -DDYNAMI C_FFI -DDYNAMIC_MODULES -c modules.c = =20 ... [Background: I'm fed up with CLISP regenerating all *.fas/*.mem when = they are not needed, while I'm playing with modules. Of course, = Makefile cannot know when it's superfluous, so it plays it safe. How = can I build a module without having every *.fas/*.mem rebuilt? ] Thanks, J=F6rg H=F6hle. |