...in my previous e-Mail I forgot to mention, that I added the two files
/etc/apache2/mods-enabled/rivet.load
LoadModule rivet_module /.../src/apache-2/.libs/mod_rivet.so
/etc/apache2/mods-enabled/rivet.conf
<IfModule mod_rivet.c>
AddType application/x-httpd-rivet .rvt
AddType application/x-rivet-tcl .tcl
</IfModule>
OK, one step further now. I created a softlink in /usr/lib/tcl8.4 called
rivet that points to the rivet directory containing the init.tcl.
When staring apache2 it looks promising:
error_log:
[Thu Apr 13 02:30:25 2006] [notice] Apache/2.0.54 (Ubuntu) Rivet configured
-- resuming normal operations
but then I got Segmentation faults accessing either plain .html or .rvt
files:
error_log:
[Thu Apr 13 02:30:40 2006] [notice] child pid 8066 exit signal Segmentation
fault (11)
Is there a way to test Rivet in an interactive shell? I tried tclsh:
# tclsh
% package require RivetTcl
1.1
% load /usr/lib/apache2/modules/mod_rivet.so
couldn't load file "/usr/lib/apache2/modules/mod_rivet.so":
/usr/lib/apache2/modules/mod_rivet.so: undefined symbol: apr_day_snames
the include directory for apr was called /usr/include/apr-0/... is this too
old?
I feel so helpless... ;-)
Holger
> -----Original Message-----
> From: Holger Zeinert [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 13, 2006 10:22 AM
> To: [EMAIL PROTECTED]
> Cc: Rivet; [EMAIL PROTECTED]
> Subject: RE: Rivet Apache 2
>
>
> So, here's what I did:
>
> - got all necessary packages
>
> - check out of current version using svn
>
> - created a tree of softlinks in /tmp/apache2:
> bin/
> including all apache* and apxs* from
> /usr/bin and /usr/sbin
> conf/
> including all files from /etc/apache2/*
> include/
> including all files from /usr/include/apache2 and
> /usr/include/apr*/*
>
> - in bin/ I created softlinks from apxs2 to apxs and
> apache2ctl to apachectl
>
> - then configure:
> ./configure --with-tcl=... \
> --with-apache=/tmp/apache2 \
> --with-apache-base-dir=/tmp/apache2 \
> --with-apxs=1
>
> - then "make"
>
> this produces some warnings, but at the end
> mod_rivet.so is created.
>
> - then "make install"
>
> This gives an error about mkinstalldirs
>
> make install
> Making install in src
> make[1]: Entering directory `/home/vmware/rivet/rivet/src'
> Making install in apache-2
> make[2]: Entering directory `/home/vmware/rivet/rivet/src/apache-2'
> make[3]: Entering directory `/home/vmware/rivet/rivet/src/apache-2'
> /bin/sh ../../tclconfig/mkinstalldirs /usr/lib/apache2/modules
> /bin/sh: ../../tclconfig/mkinstalldirs: No such file or directory
> make[3]: *** [install-apxs_libexecLTLIBRARIES] Error 127
> make[3]: Leaving directory `/home/vmware/rivet/rivet/src/apache-2'
> make[2]: *** [install-am] Error 2
> make[2]: Leaving directory `/home/vmware/rivet/rivet/src/apache-2'
> make[1]: *** [install-recursive] Error 1
> make[1]: Leaving directory `/home/vmware/rivet/rivet/src'
> make: *** [install-recursive] Error 1
>
> and in fact the file mkinstalldirs is not included in my tclconfig
> directory. Where do I get it? Also in older tar files, I did
> not find this
> file.
>
> Is there an easy way to do the install manually? I got mod_rivet.so
> activated, but it did not find the init.tcl stuff. So,
> perhaps I can do this
> manually, but how...
>
> Any idea?
>
> Regards
> Holger
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, April 05, 2006 6:33 PM
> > To: Holger Zeinert
> > Cc: Rivet
> > Subject: Re: Rivet Apache 2
> >
> >
> > Holger Zeinert schrieb:
> > > [Sun Apr 02 16:24:20 2006] [error] (20014)Error string not
> > specified yet:
> > > init.tcl must be installed correctly for Apache Rivet to
> > function: can't
> > > find package RivetTcl 1.1
> > >
> > Can you post more concrete output? I assume, the autoconf/automake
> > issues are not figured out yet completely.
> > > The only question I have right now: does it make sense to
> > test the Apache2
> > > part? I'm willing to do some tests, but if you are saying
> > that this is too
> > > early, I will come back later.
> > >
> >
> > I think it is too early for a release, some things still have
> > to be done
> > resp. need more testing and polish. But if you like to test or even
> > participate in development, you are welcome ;-).
> >
> >
> > Eckhard
> >
>
> ---------------------------------------------------------------------
> 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]
