Hi Jeff

you're absolutely right and thank you very much for the suggestion. I was
reading the header in install-sh and found out it came from X11R5, that is
before the last ice age, in the context of free software history.

I will work on it.

 -- Massimo

P.S. Btw, when you make an rpm out of rivet would you tell us where it's
located so that we can add a link on the website?

On Thu, 6 May 2010 10:06:59 -0500, Jeff Lawson wrote
> 2010/5/6 Massimo Manghi <[email protected]>:
> > 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
> >
> 
> This is due to the tclconfig/install-sh script that is part of TEA is
> extremely old (its file header says 1989).  autoconf expects a more
> functional install-sh script, and a much better version is normally
> delivered with any recent version of autoconf.  If you search your
> system and exclude directories named "tclconfig", you'll likely find
> several other newer versions of this script that can be used as a
> replacement.
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to