9.2.1 compile on foo, install on bar

Joseph S D Yao jsdy at center.osis.gov
Tue Jun 4 16:41:31 UTC 2002

On Tue, Jun 04, 2002 at 11:52:49AM -0400, Kevin Butnik wrote:
> I have a couple of Solaris 2.6 systems, one of which handles compiling =
> (gcc,
> gnu make, so on installed).  I would like to create a nice tar file that =
> I
> could create on the compile box (foo) in order to install the BIND =
> binaries
> on the non-compile box (bar).  Foo and bar have the same system setup.  =
> What
> files do I need to include in my tar to upgrade bar to 9.2.1 (from 8.x)?
> Better yet, is there a nice 3rd party package (or a make command in the =
> release) to do this for me? =20
> Thanks,
> Kevin Butnik

I'm abpout to modify 'configure' and 'make/rules.in' to make that
automatic, and I hope I get time to send in the [relatively simple]
mods.  For the time being, do this:

	Pick an empty directory in which to "install" the package,
	e.g., "/tmp/bind9".

	In make/rules.in, change
		DESTDIR = /tmp/bind9
	using, of course, the directory name you have chosen.

	Determine whether you had been installing BIND 8 in, e.g.,
	/usr/bin and /usr/sbin or /usr/local/bin and /usr/local/sbin.

	If you have done a previous 'configure' or 'make', run 'make
	clean' and remove config.h, config.log, config.cache,
	config.status, and isc-config.sh.  I'm sure that some of this
	does NOT have to be removed, but I'm trying to go back to
	something closer to the original state.

	Run 'configure' using the appropriate prefices, e.g.:
		cd /usr/src/import/bind-9.2.1
		./configure --prefix=/usr ...

	Run 'make' and 'make install' - should put it in the chosen
	directory.  "Should".  I haven't actually gotten BIND 9 to
	do this yet, but I've decided that's how it will work, today.

	cd /tmp/bind9; tar cf - . | gzip > /tmp/bind9.tgz

Joe Yao				jsdy at center.osis.gov - Joseph S. D. Yao
OSIS Center Systems Support					EMT-B
   This message is not an official statement of OSIS Center policies.

More information about the bind-users mailing list