Thanks Yorick, I'm going to check the patch and commit it to both branches/2.2 and trunk, but it looks OK to me
-- Massimo On 01/03/2015 04:18 PM, Poor Yorick wrote: > Hi, > > An attempt to building rivet-2.2.0 resulted in the following error: > > libtool: compile: gcc -m64 > -specs=/path/to/tcl_rivet-2.2.0-tcl-8.5.17/gccspecs/specs > -DHAVE_CONFIG_H -I. -I.. -Iapache-2 -Ichannel -Iparser -Irequest > -I/path/to/apache_httpd-2.2.27-default/include > -I/tmp/tcl_rivet-2.2.0-tcl-8.5.17/rivet-2.2.0/src > -I/path/to/tcl-8.5.17-default/include -fpic > -I/path/to/apache_httpd-2.2.27-default/include -DLINUX -D_REENTRANT > -D_GNU_SOURCE -I/path/to/apr-1.5.1-default/include/apr-1 > "-DSTART_TAG=\"<?\"" "-DEND_TAG=\"?>\"" -fpic -pipe -O2 > -fomit-frame-pointer -Wall -fPIC -isystem > /tmp/tcl_rivet-2.2.0-tcl-8.5.17 -isystem > /path/to/tcl_rivet-2.2.0-tcl-8.5.17/include -isystem > /path/to/i64f6m13s1l2618c25e/include -MT > request/mod_rivet_la-apache_multipart_buffer.lo -MD -MP -MF > request/.deps/mod_rivet_la-apache_multipart_buffer.Tpo -c > request/apache_multipart_buffer.c -fPIC -DPIC -o > request/.libs/mod_rivet_la-apache_multipart_buffer.o > In file included from > /path/to/apache_httpd-2.2.27-default/include/httpd.h:43, > from request/apache_request.h:4, > from request/apache_multipart_buffer.h:21, > from request/apache_multipart_buffer.c:25: > /path/to/apache_httpd-2.2.27-default/include/ap_config.h:26:23: > error: apr_hooks.h: No such file or directory > > > The problem is that in this particular software collection, each software > distribution is installed into an isolated directory, and the header > files for > apr-utils are not in the same directory as the header files for apr. > Modifying > the autoconf and automake files to treat those two sets of headers > separately > solved the problem. The attached patch has the details. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
