Paul Bijnens said: 
> todd zenker wrote:
> 
> > I'm trying to compile the amanda-2.4.4.p1 client on Solaris 
> 9 and it 
> > stops at config.status: executing depfiles commands.

> If you're compiling anyway, why did you choose an old version?
> Current stable is 2.4.4p3.

Todd -

Definitely get 2.4.4p3, 2.4.4p1 on Solaris is unable to find the
readline include files even if you give the location to configure.  (If
you MUST use 2.4.4p1, link /usr/local/include/readline to
amanda-2.4.4p1/common-src/readline.)

2.4.4p3 is NOT available at ftp.amanda.org, but it is available via
HTTP.  (Is there someone on this list who can fix that BTW?)

For client only, I compile with --with-user=amanda --with-group=sysadmin
--with-smbclient=/usr/local/bin/smbclient
--with-gnutar=/usr/local/bin/tar --with-libraries=/tmp/lib
--with-include=/tmp/include --without-server --without-restore

I like to use /tmp/lib and /tmp/include instead of
/usr/local/[lib|include] when compiling because I build packages for
distribution to 20+ hosts and it helps me manage dependancies.

2.4.4p3 compiles fine for me on Solaris 9 - I'm compiling my client
today actually.  I could probably send you a client package for p1 or p3
in Solaris package format - although the p1 would have group=sysadmin
and the p3 package wouldn't be tested yet.

To compile or run on Solaris, you will also need SUNWgzip (preferable
over the Sunfreeware gzip), SMCreadl (or compile the GNU readline
libraries yourself), and libgcc if you use gcc.


Jon LaBadie said:

> You say there is "no make to run".
> Do you really mean "make" or "no makefile (or Makefile)"?
> One is a program that must be installed as a system developer utility,
> the other is the control file created by configure.
> 
> If you really mean "make" the program, as in "$ bash: make: 
> not found",
> then you probably do not have your PATH variable set properly.  Copies
> can be found in /usr/ccs/bin and /usr/xpg4/bin.  They are installed
> with the packages SUNWsprot and SUNWxcu4t respectively (check with
> pkginfo if they are installed).  A copy of GNU's make can also be
> installed (I "think" used with amanda) from the "Companion CD" (CCD).
> It gets insatlled in /opt/sfw/bin as "gmake" from package SFWgmake.

If you are compiling anything on Solaris, you pretty much need to have
/usr/ccs/bin in your path.


> Sun doesn't supply a C compiler so unless you purchase an extra
> cost compiler, you will have to install the GNU C compiler (gcc)
> from the CCD.  On a standard installation Sun puts a shell script
> called "cc" in /usr/ucb directory; all it does is say is "you don't
> have a compiler".  When I install the GNU compilers I then rename
> /usr/ucb/cc and replace it with a symbolic link to /opt/sfw/bin/gcc.
> I put similar links in /usr/ccs/bin and /opt/sfw/bin.

I'd highly recommend against removing the existing /usr/ucb/cc, because
it can lead to confusion about which compiler you are using and there
are a number of cases where it matters whether you use the Sun compilier
or gcc (particularly when building perl modules).  Also, Sun may replace
/usr/ucb/cc with a patch or upgrade and when you remove an individual
file that is part of a package, you've essentially broken your package
database.

I prefer to set CC=gcc in my .profile/.cshrc and then always use make to
compile even if all I use is the default rules. ("touch Makefile; make
foo" or "make -f /dev/null foo" will compile foo.c into a binary called
foo when compiling something too simple to need a Makefile")

Julie