Jean-Louis Martineau wrote:
Hi Weihai,

Could you provide more informations?

Your configure command line?
./configure --with-suffixes=yes --with-user=amanda --with-group=operator --with-tape-device=/dev/nrsa0 --with-fqdn --with-gnutar=/usr/local/bin/gtar --with-gnutar-listdir=/usr/local/var/amanda/gnutar-lists
Which Arch/OS?
Freebsd 4.6 stable
Which sed are you using? You should try gnu sed.
Default  /usr/bin/sed. Do I need gsed?
What's the value of 'transform' in you Makefile?
transform = s,$$,-2.4.3,;
Could you also include more line of the output of make, it's easier
to find the problem if I know which command break.
output of "make install#
Making install in config
Making install in common-src
/bin/sh ../config/mkinstalldirs /usr/local/lib
 /bin/sh ../libtool --mode=install /usr/bin/install -c  libamanda.la /usr/local/lib/libamanda.la
/usr/bin/install -c .libs/libamanda.lai /usr/local/lib/libamanda.la
/usr/bin/install -c .libs/libamanda.a /usr/local/lib/libamanda.a
ranlib /usr/local/lib/libamanda.a
chmod 644 /usr/local/lib/libamanda.a
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/local/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,--rpath -Wl,LIBDIR' linker flag

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
Making install in client-src
/bin/sh ../config/mkinstalldirs /usr/local/lib
 /bin/sh ../libtool --mode=install /usr/bin/install -c  libamclient.la /usr/local/lib/libamclient.la
/usr/bin/install -c .libs/libamclient.lai /usr/local/lib/libamclient.la
/usr/bin/install -c .libs/libamclient.a /usr/local/lib/libamclient.a
ranlib /usr/local/lib/libamclient.a
chmod 644 /usr/local/lib/libamclient.a
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/local/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,--rpath -Wl,LIBDIR' linker flag
See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
/bin/sh ../config/mkinstalldirs /usr/local/libexec
sed: 1: "s,$,-2.4.3,;;s/$//": invalid command code ;
*** Error code 1

Stop in /usr/local/src/amanda-2.4.3/client-src.
*** Error code 1

Stop in /usr/local/src/amanda-2.4.3/client-src.
*** Error code 1

Stop in /usr/local/src/amanda-2.4.3.


Thanks

--weihai

Jean-Louis

On Wed, Oct 09, 2002 at 01:49:45PM +0200, weihai Pan wrote:
  
Hi,

I upgrade amanda from 2.4.2p2 to 2.4.3. when I make install, there are
the following error:


/bin/sh ../config/mkinstalldirs /usr/local/libexec
sed: 1: "s,$,-2.4.3,;;s/$//": invalid command code ;
*** Error code 1
Stop in /usr/local/src/amanda-2.4.3/client-src.


When I use gmake, the error is still there but install binaty on right
place. But the suffixes disappear.

could anyone tell your success?

Thanks.

--weihai


    

  

Reply via email to