From: Forest W <lyr...@ww...> - 2003-03-26 00:09:07
|
Andreas sent his build output to show that tclxml will build with expat, which is good to know, but it doesn't really help me. I'm not doing an automated build with complex directory structure like he is. I'm just following the build instructions in the README, and it doesn't work on red hat 7.3. Even with the copy of tclxml that I checked out from CVS 30 minutes ago, "make all" in tclxml/expat fails while trying to find .c and .h files that exist in the parent directory. As an experiment, I copied all the .c and .h files from the tclxml dir to the expat dir, and tried "make" again. It worked. =20 Another experiment: I noticed that expat/Makefile sets the VPATH to /..:$(srcdir)/xmltok:$(srcdir)/xmlwf:$(srcdir)/xmlparse I removed the leading / so .. would be the first element in VPATH. That worked too. Okay, so it appears that the problem is that expat/Makefile doesn't know how to find the files that live in the parent dir. I don't understand how it ever finds them, since that leading '/' in the VPATH appears to be preventing it. Is that '/' a bug? Side note: The README file refers to the --exec_prefix switch for configure, while the configure help refers to --exec-prefix. Notice the difference between underscore and dash. I guess configure may be forgiving about this, but even if it is, the discrepency is confusing. >Excerpt of ActiveState ActiveTcl build done last night, linux. >Some commands are intentionally broken over several lines to make >them more readable. > >First tclxml, then tclxml/expat. > >For comparison with your logs. As you can see I did not have the >problem you saw. > >/nfs/crimper/home/andreask/activetcl/dbn/lba/pliers/night/builds/linux-i= x86/ >is the main build directory and can be replaced with something shorter = for >readability. |