On Thursday 20 June 2002 10:48, Allan Sun wrote:
>Hi all,
>I just downloaded 2.4.2p2 on my Mandrake 8.2(Linux kernel 2.4.18),
>I got the following error when run
>#./configure
>
>checking host system type... configure: error: can not guess host
> type; you must specify one
>
>Coud somebody help me?
>
>Thanks a lot,
You're going to need a lot more to configure than that for amanda,
she is a bit picky.
However the fact that you're getting this particular error tends to
make me think that the full complement of developer stuff is not
installed on your machine. Some of the softlinks to the includes
that normally get made when compiling a kernel are on the missing
list, and its usually these that help the configure script to
properly define the system its being built on.
Aside from that, there are a few other arguments to the configure
script that also need defined, and which should remain consistent
(unless there is a very good reason to change them) from amanda
build to amanda build. I mention that because amanda is a moving
target, getting new features, or ways to do things, added with
almost every release. 99% of the time the same old operating
configs can be used, and this means a new version of amanda can be
built, installed, and you can goto bed confident that the lady will
wake up and do her job on time without requireing human
intervention.
Just as an example of all the arguments that ./configure needs for a
semi-normal amanda build and install, here is my script that drive
the configure program, if you like it, save it, set the +x bit with
chmod, and run it as ./whatever_name_you_saved_it_as:
=====================
#!/bin/sh
make clean
rm -f config.status config.cache
./configure \
--with-user=amanda \
--with-group=disk \
--with-owner=amanda \
--with-tape-device=/dev/nst0 \
--with-changer-device=/dev/sg1 \
--with-gnu-ld --prefix=/usr/local \
--with-debugging=/tmp/amanda-dbg/ \
--with-tape-server=192.168.1.3 \
--with-amandahosts \
--with-configdir=/usr/local/etc/amanda
===========================
I have a tape changer robot, if you don't have that, then delete the
line defining the changer-device and make the required changes to
the rest of the .conf files amanda uses.
This script won't work for 95% of the users, but it gives you an
idea of what all needs to be defined, and defined for every build
of amanda. Once you arrive at a configuration thatw orks for you,
copy it over to the new directory and run it as the first thing
after unpacking the new sources each time.
To do a proper build and install, you'll be bouncing in and out of
users to root and back. Best built in
/home/amanda/amanda-version-number,
unpack it as root, cd to the directory you have, then do a "chmod -R
amanda:disk * "
The "su amanda", giving the password you gave her, and run the
personalised version of the above script. When thats done, issue
a "make" while you are still user amanda.
When thats done, "su -" and give roots password, then cd to this
same directory and issue a "make install", where the install script
will then handle all the various permission setting and such that
amanda needs.
All of this is of course in the docs, so I'm wasting bandwidth, but
a refresher aimed at the new bee has been known to help, and I hope
this does.
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.0% setiathome rank, not too shabby for a WV hillbilly
