From: Maurice L. <mj...@ga...> - 2002-01-15 05:53:34
|
Maurice LeBrun writes: > Alan W. Irwin writes: > > If changing my mind is no problem to cvs (meaning I can always go back if > > there is a storm of protest), then I think the right thing to do is to treat > > these generated files the same way we do the configure script; exclude them > > from cvs control but generate them for the tarball release. This only puts > > the onus on those of us here on the developer's list (and perhaps a few > > more) that are building from CVS to be sure that they have perl. > > I don't see any problem with this. Previously, it was leaving the generated > files out of the public distribution that caused all the trouble. Well right off I hit a problem (first plplot build I've tried in a while). There is a catch-22 with the build process: the necessary header files get built *after* the symlinks into tmp/plplot are created, so they are not found. E.g. on a fresh build: ... gcc -c -g -O -I. -I/home/mjl/gts/include plimage.c cd /home/mjl/dev/plplot/latest/bindings/tcl; \ perl pltclgen cd /home/mjl/dev/plplot/latest/bindings/tcl; \ perl pltclgen cd /home/mjl/dev/plplot/latest/bindings/tcl; \ perl pltclgen gcc -c -g -O -I. -I/home/mjl/gts/include tclAPI.c tclAPI.c:35:27: plplot/tclgen.h: No such file or directory tclAPI.c:70:29: plplot/tclgen_s.h: No such file or directory tclAPI.c:478:20: tclgen.c: No such file or directory make: *** [tclAPI.o] Error 1 Running configure again "solves" this problem, but a nicer solution should be found. -- Maurice LeBrun mj...@ga... |