Brian Cuttler wrote:

bali 16# make install
Making install in config
Making install in common-src
        /bin/sh ../config/mkinstalldirs /usr/local/lib
 /bin/sh ../libtool --mode=install /usr/local/bin/install -c  libamanda.la 
/usr/local/lib/libamanda.la
/usr/local/bin/install -c .libs/libamanda-2.4.4p1-20030716.so 
/usr/local/lib/libamanda-2.4.4p1-20030716.so
/usr/local/bin/install: can't open libamanda-2.4.4p1-20030716.so: No such file or 
directory.


I have no experience with Irix, but it seems that configure
got the wrong syntax for the current install program used.

GNU fileutils 4.1 install program has syntax:

    /usr/bin/ginstall -c  file dest
        (the -c option is ignored - just for compatibility)

install as found Solaris 2.8:

/usr/sbin/install -c dira file

     -c dira
           Install file in the directory specified  by  dira,  if
           file  does  not  yet  exist.  If  it is found, install
           issues a message saying that the file already  exists,
           and exits without overwriting it.


The install you use on Irix seems to follow the Solaris convention while, when I run configure on Solaris is uses "config/install-sh" and not the system supplied install.

You did a "make distclean" before you compiled the program, did you?

Maybe just rename the /usr/local/bin/install (temporarily) before
so that even configure cannot find it?


-- Paul Bijnens, Xplanation Tel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *********************************************************************** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***********************************************************************




Reply via email to