Hi Harald
thank you for the feedback. I assume you got a working installation though
On 05/06/2010 11:40 AM, Harald Oehlmann wrote:
Thank you for Rivet 2.0 release.
On SuSE 11.1 Linux 32 bit x86:
./configure --with-tcl=/usr/lib --with-apache-version=2
--with-tclsh=/usr/bin/tclsh --with-apache=/usr
--with-rivet-target-dir=/usr/lib/myrivetlib --with-apxs=/usr/sbin/apxs2
make ->ok
make install
...
/bin/sh /home/oehhar/test/rivet-2.0.0/tclconfig/install-sh -d
/usr/lib/myrivetlib
basename: Invalid option -- d
mv: Invalid Option -- d
true, this happened to my installations too, but it was harmless and
eventually I forgot about it.
We probably have to revise the tools we have for moving the files to
their final place, but since after all I could live with it I lose
motivation in tackling the problem
The shell script:
rivet-2.0.0/tclconfig/install-sh
is called with the option -d
IMHO this shell script does not have the option -d.
In consequence, -d is taken as a source file and passed to "mv", which
complains about an invalid option.
This is the first of a set of errors following (many times like:
error while sourcing packages/dio/pkgIndex.tcl: can't read "dir": no
such variable).
I suppose, the folder "myrivetlib" should be created.
This is done, or, at least, it exists after the install with a lot of
IMHO meaningful contents.
yes, true. If files are in this directory chances are you got a working
installation of Rivet.
After you configured apache to the module and properly handle .tcl and
.rvt files, you may check if Rivet Tcl stuff was properly installed
putting the following code in an .rvt file
<?
package require Rivet
package require Session
package require DIO
package require form
puts "<b>I got right here!</b>"
?>
should display the bottom line without stubling in an error of "can't
find package ..."
I have the whole log, if interested, I may post it.
yes, would you send it over to me in a private mail?
-- Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
