Here is output of `./configure': checking for gtar... no checking for gnutar... /usr/bin/gnutar configure: WARNING: *** /usr/bin/gnutar is not GNU tar, so it will not be used. The script search for `gtar gnutar tar' in $PATH. Search stopped if one found. /usr/bin/gnutar is a part of `star' package so it is not GNU tar program and is not used by amanda. This can be easily fixed by this patch: --- amanda-2.4.4_p2-r1.ebuild.orig 2004-10-09 12:35:23.000000000 +0800 +++ amanda-2.4.4_p2-r1.ebuild 2004-10-09 12:36:24.000000000 +0800 @@ -170,6 +170,8 @@ # Samba support use samba && myconf="${myconf} --with-smbclient=/usr/bin/smbclient" || myconf="${myconf} --without-smbclient" + myconf="${myconf} --with-gnutar=/bin/tar" + econf ${myconf} || die "econf failed!" emake || die "emake failed!" Reproducible: Always Steps to Reproduce: 1. emerge sync 2. emerge star 3. emerge amanda Actual Results: checking for gtar... no checking for gnutar... /usr/bin/gnutar configure: WARNING: *** /usr/bin/gnutar is not GNU tar, so it will not be used. Expected Results: checking for gtar... /bin/tar
fixed in cvs.
If you mean patch-tar-1.14.90 then it is not fixed the problem. Please change ebuild as specified in my bugreport. Amanda's `configure' script search for 3 names in `$PATH' - `gtar', `gnutar', `tar', in that order. It find `gnutar' (from star package), then check that it is not `GNU tar' and search stopped. It does not even try seearching for `tar' executable in `$PATH'. `--with-gnutar' option change this behavior - `configure' script check specified only binary.
my bad. there was another very similar bug report to this due to tar-1.14.90 where your solution here was suggested. fixed properly in cvs now (with your patch).
