David Brancato wrote: > The latest svn code compiles fine (actually, I had to install xsltproc then > recompile, configure never warned about its absence. Also, contrary to the > README.configure, I have to run autoheader before I run automake).
Hrm... I'll have to look at that, as that should be completely optional. I don't want to require too many build dependencies just to hack on the code. > "make install" yields: What system was this, again? > Making install in src > make[1]: Entering directory `/home/david/svn/tcl-rivet/src' > make[2]: Entering directory `/home/david/svn/tcl-rivet/src' > test -z "/usr/local/apache/libexec" || mkdir -p -- "/usr/local/apache/libexec" > /bin/sh ../libtool --mode=install /usr/bin/install -c 'mod_rivet.la' > '/usr/local/apache/libexec/mod_rivet.la' > /usr/bin/install -c .libs/mod_rivet.so /usr/local/apache/libexec/mod_rivet.so > /usr/bin/install -c .libs/mod_rivet.lai /usr/local/apache/libexec/mod_rivet.la > PATH="$PATH:/sbin" ldconfig -n /usr/local/apache/libexec > ---------------------------------------------------------------------- > Libraries have been installed in: > /usr/local/apache/libexec > > If you ever happen to want to link against installed libraries > in a given directory, LIBDIR, you must either use libtool, and > specify the full pathname of the library, or use the `-LLIBDIR' > flag during linking and do at least one of the following: > - add LIBDIR to the `LD_LIBRARY_PATH' environment variable > during execution > - add LIBDIR to the `LD_RUN_PATH' environment variable > during linking > - use the `-Wl,--rpath -Wl,LIBDIR' linker flag > - have your system administrator add LIBDIR to `/etc/ld.so.conf' > > See any operating system documentation about shared libraries for > more information, such as the ld(1) and ld.so(8) manual pages. > ---------------------------------------------------------------------- > test -z "/usr/lib /usr/share/rivet" || mkdir -p -- "/usr/lib /usr/share/rivet" > /bin/sh ../libtool --mode=install /usr/bin/install -c 'librivet.la' > '/usr/lib /usr/share/rivet/librivet.la' > /usr/bin/install -c .libs/librivet.so /usr/lib /usr/share/rivet/librivet.so > /usr/bin/install: installing multiple files, but last argument, > `/usr/share/rivet/librivet.so' is not a directory > Try `/usr/bin/install --help' for more information. > /bin/sh ../libtool --mode=install /usr/bin/install -c 'librivetparser.la' > '/usr/lib /usr/share/rivet/librivetparser.la' > /usr/bin/install -c .libs/librivetparser.so /usr/lib > /usr/share/rivet/librivetparser.so > /usr/bin/install: installing multiple files, but last argument, > `/usr/share/rivet/librivetparser.so' is not a directory Ugh... that's just weird. > Try `/usr/bin/install --help' for more information. > make[2]: *** [install-lib_libexecLTLIBRARIES] Error 1 > make[2]: Leaving directory `/home/david/svn/tcl-rivet/src' > make[1]: *** [install-am] Error 2 > make[1]: Leaving directory `/home/david/svn/tcl-rivet/src' > make: *** [install-recursive] Error 1 > > > In the meantime, can someone shoot me a quick list of what goes where and > I'll manually copy them. /rivet/ is a directory that Tcl looks in as part of it's package path. For example: /usr/lib/rivet/librivet.so /usr/lib/rivet/librivetparser.so although I see that things still aren't quite right as the pkgIndex.tcl file isn't being generated quite right. Ugh:-( -- David N. Welton - http://www.dedasys.com/davidw/ Apache, Linux, Tcl Consulting - http://www.dedasys.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
