Date: Thu, 14 Oct 1999 11:52:17 -0700 From: Byron Young <bkyoung@jps.net> To: Bohdan Tashchuk <tashchuk@easystreet.com>, freebsd-questions@freebsd.org Subject: Re: Applying bind8 port Message-ID: <38062661.AFD4141@jps.net> References: <3802360A.F9522F4D@jps.net> <3802E9AA.62C5B711@easystreet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for replying Bohdan. Bohdan Tashchuk wrote: > > I'm just a FreeBSD newbie, so I can't tell you why your build failed. So am I and me neither!!! > > But I can tell you that I successfully built Bind 8.2.1 on FreeBSD 3.3 > release without any problems. The best I can do is tell you what I did > and how it differs from what you did. Thats great that you were successful, and thanks for this info. > 1) Target machine was an old P100 with limited disk space, so I don't > have ports installed. I followed directions in The Complete FreeBSD book > to unpack the specific package from the tarball on the CD. I also had to > unpack the Mk package, that's not stated clearly. Target machine has ports package installed and the make package is properly? installed. However, the target machine's original install was 3.1-RELEASE from the Walnut Creek CDROM and 3.3-RELEASE was cvsup'ed from ftp.freebsd.org. > 2) I used the script command ahead of time, so I now have a better record > of what happened. This is what allows me to tell you what I did. > Yes, I must get in the habit of using it more often. > 3) I allowed the make procedure to FTP the files directly from ftp.isc.org I manually retrieved, from ftp.isc.org, /isc/bind/src/8.2.1/bind-doc.tar.gz /isc/bind/src/8.2.1/bind-src.tar.gz into /usr/ports/disfiles (I'm just more comfortable doing it that way) The datestamp for bind-doc.tar.gz is Jun 21 13:25 The datestamp for bind-src.tar.gz is Jun 21 13:25 The datestamp for the bind-doc.tar.gz I ftp'd from ftp.freebsd.org was Jun 21 14:25 Dosn't seem to be any difference. Apply attempt on target machine with new .tar.gz files failed. :( > 4) I have a firewall installed (in fact the FreeBSD machine IS my firewall > machine) so I had to add > > setenv FTP_PASSIVE_MODE yes > > before I typed make. I also had to add a $fwcmd rule to allow FTP from > ftp.isc.org to me. > > 5) my "diffs" didn't try to patch as much as yours did. In particular my > diffs didn't try to patch the getpwent.c file that yours failed with. > I think that either the ports tarball you are using is out of date or > the starting src files are. To resolve any doubt, I downloaded the most recent ports.tgz file from ftp.freebsd.org/pub/FreeBSD/releases/i386/3.3-RELEASE/ports into /usr/ports/distfiles and then extracted the bind8 port using cd /usr tar xzvf /usr/ports/distfiles/ports.tgz ports/net/bind8 after the extraction completed, I cd /usr/ports/net/bind8 make clean make Result was the same.... ===> Extracting for bind-8.2.1 >> Checksum OK for bind-src.tar.gz. >> Checksum OK for bind-doc.tar.gz. ===> Patching for bind-8.2.1 ===> Applying FreeBSD patches for bind-8.2.1 Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |--- src/port/freebsd/Makefile.set.orig Mon Jun 16 23:30:35 1997 |+++ src/port/freebsd/Makefile.set Tue Nov 25 18:51:41 1997 -------------------------- Patching file src/port/freebsd/Makefile.set using Plan A... Hunk #1 succeeded at 1. Hunk #2 succeeded at 18. done Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |--- doc/man/Makefile.orig Fri Mar 14 04:43:51 1997 |+++ doc/man/Makefile Mon Jan 5 14:03:46 1998 -------------------------- Patching file doc/man/Makefile using Plan A... Hunk #1 succeeded at 52. Hunk #2 succeeded at 105. done Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |--- src/lib/irs/getpwent.c.orig Wed May 20 21:18:51 1998 |+++ src/lib/irs/getpwent.c Wed May 20 21:21:21 1998 -------------------------- Patching file src/lib/irs/getpwent.c using Plan A... Hunk #1 failed at 102. 1 out of 1 hunks failed--saving rejects to src/lib/irs/getpwent.c.rej done *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. >Here is the relevant snippet from my efforts: > > ===> Extracting for bind-8.2.1 > >> Checksum OK for bind-src.tar.gz. > >> Checksum OK for bind-doc.tar.gz. > ===> Patching for bind-8.2.1 > ===> Applying FreeBSD patches for bind-8.2.1 > Hmm... Looks like a unified diff to me... > The text leading up to this was: > -------------------------- > |--- src/port/freebsd/Makefile.set.orig Mon Jun 16 23:30:35 1997 > |+++ src/port/freebsd/Makefile.set Tue Nov 25 18:51:41 1997 > -------------------------- > Patching file src/port/freebsd/Makefile.set using Plan A... > Hunk #1 succeeded at 1. > Hunk #2 succeeded at 18. > done > Hmm... Looks like a unified diff to me... > The text leading up to this was: > -------------------------- > |--- doc/man/Makefile.orig Fri Mar 14 04:43:51 1997 > |+++ doc/man/Makefile Mon Jan 5 14:03:46 1998 > -------------------------- > Patching file doc/man/Makefile using Plan A... > Hunk #1 succeeded at 52. > Hunk #2 succeeded at 105. > done > ===> Configuring for bind-8.2.1 > ===> Building for bind-8.2.1 > > 6) You are being hopelessly optimistic by de-configuring named in your > rc.conf and then rebooting. It is an unfortunate fact that this version > of bind installs itself into /usr/local and so won't overwrite existing > binaries. Someone on this list responded to my complaint about where the > files were put by telling me: > > To start the new named, add the following to /etc/rc.conf.local: > > named_program="/usr/local/sbin/named" > named_flags="-c /etc/namedb/named.conf -u bind -g bind" > named_enable="YES" > > Regards > > ------------------------------------------------------------------------- > Udo Schweigert || Voice : +49 89 636 42170 > Siemens AG, Siemens CERT || Fax : +49 89 636 41166 > ZT IK 3 || email : Udo.Schweigert@mchp.siemens.de > D-81730 Muenchen / Germany || : ust@cert.siemens.de > > 7) The advice given in #6 makes a lot of sense and is less work. But I > chose > to not follow it, because it bugs me that all the old binaries were lying > around and I had to be careful about path to avoid the old ones. So in > /var/db > there is a log of what files were added. I found all the old binaries and > moved > them to *.old. Eg, I now have a /usr/sbin/named.old and > /usr/local/sbin/named. That file I guess is /var/db/pkg/bind-8.2.1/+CONTENTS on this system and shows a lot of files. That must have taken some time! The file has a @cwd /usr/local line. I am assuming that means changed working directory to /usr/local. Funny thing is that the named binary in the /usr/local/sbin directory has a date stamp prior to my 3.3-RELEASE update. Must have originated from a pkg_add command somewhere. I renamed it to named002 (the origional named in /usr/sbin is named001). Now more wierdstuff. The boot information printed in /var/log/messages shows the date for named to be the date I updated to 3.3-RELEASE, not the date of named in /usr/sbin. This is all too complex for me so I'll just buy the CDROM for some upcoming X.Y RELEASE. > I haven't updated the manuals this way yet, because it's not immediately > obvious that the latest port has all the latest manuals. For example, when > I > diffed them I saw some typos fixed in the old version but not in the new. > > 8) If you don't set the -c flag as shown in item #6 you will need to create > /etc/named.conf instead as that is the compiled default, which differs from > the old version. > > 9) I actually typed > > make > make install > make post-install > > I divined this last step from perusing the makefile. It seems to do some > cleanup and some additional "install". I'm not sure if it's needed or if > I made things worse, but I did it anyway. I didn't see any documentation > about what that step does. > At this point, I decided to reinstall the bind 8.1.2 port from the 3.1-RELEASE Walnut Creek CDROM. The build was successful and it successfully diffed the getpwent.c file. However, a cd /usr/sbin ls -al bind* indicated that the named file hadn't been updated. The datestamp still indicated the origial install date. Some reverse disassembly of the make files led me to "divine" that a make afterinstall was required. That put a new named into /usr/sbin, I am just hoping that it is the newly built named and not a copy of some other named. > 10) This is the most important part. The old bind 8.1.2 that comes with > FreeBSD 3.3 Release seemed to occasionally ignore requests from my internal > net. It would see the request from the internal net, ask the outside world > (forward only), see the response, and then forget to tell the internal net > until 5 seconds later when internal net timed out and asked again. I'll just deal with it. Thanks again, Byron > > The new bind 8.2.1 doesn't have this bug and has been wonderful. > > Hope this helps. > > Bohdan Tashchuk > > Byron Young wrote: > > > > Hello all, > > > > After downloading (as root) > > ftp.freebsd.org/pub/FreeBSD/distfiles/bind-doc.tar.gz > > ftp.freebsd.org/pub/FreeBSD/distfiles/bind-src.tar.gz > > > > into /usr/ports/distfiles > > > > then "tarballing" the bind8 port via ftp from > > ftp.freebsd.org/pub/FreeBSD/ports/net > > using > > ftp> get bind8.tar > > > > then extracting the skeleton files from the bind8.tar file into > > /usr/ports/net > > using > > cd /usr/ports/net > > tar xvf /usr/ports/net/bind8.tar > > > > then commenting the following lines in rc.conf > > # named_program="/usr/sbin/named" > > # named_enable="YES" > > # named_flags="-c /etc/namedb/named.conf -u bind -g bind" > > > > then rebooting with shutdown -r now > > > > then making the port by > > cd /usr/ports/net/bind8 > > make clean > > make > > > > I get the following result: > > > > ===> Extracting for bind-8.2.1 > > >> Checksum OK for bind-src.tar.gz > > >> Checksum OK for bind-doc.tar.gz > > ===> Patching for bind-8.2.1 > > ===> Applying FreeBSD patches for bind-8.2.1 > > *** Error code 1 > > > > Stop. > > > > Then, more info is written to console > > > > Hmm... Looks like a unified diff to me... > > the text leading up to this was: > > ---------------------------- > > |--- src/port/freebsd/Makefile.set.orig Mon Jun 16 23:30:35 1997 > > |+++ src/port/freebsd/Makefile.set Tue Nov 25 18:51:41 1997 > > ---------------------------- > > Patching file src/port/freebsd/Makefile.set using Plan A... > > Hunk #1 succeeded at 1. > > Hunk #2 succeeded at 18. > > done > > Hmm... Looks like a unified diff to me... > > the text leading up to this was: > > ---------------------------- > > |--- doc/man/Makefile.org Fri Mar 14 04:43:51 1997 > > |+++ doc/man/Makefile Mon Jan 5 14|03:46 1998 > > ----------------------------- > > Patching file doc/man/Makefile using Plan A... > > Hunk #1 succeeded at 52. > > Hunk #2 succeeded at 105. > > done > > Hmm... Looks like a unified diff to me... > > the text leading up to this was: > > ---------------------------- > > |--- src/lib/irs/getpwent.c.orig Wed May 20 21:18:51 1998 > > |+++ src/lib/irs/getpwent.c Wed 20 21:21:21 1998 > > ----------------------------- > > Patching file src/lib/irs/getpwent.c using Plan A... > > Hunk #1 failed at 102. > > 1 out of 1 hunks failed--saving rejects to src/lib/irs/getpwent.c.rej > > done > > > > After inspecting PLIST, the libs libbind.a and > > libbind_r.a appear to be necessary. The install > > target system is 3.3 RELEASE and appears to have > > neither of these in /usr/lib or in /usr/src/lib. > > Only libbind is in /usr/src/lib. > > > > Question: > > Are these messages a result of the missing libs? > > > > If yes, what is the best source of these libs? What > > is the best install procedure for them onto the target > > system? > > > > If these messages are not caused by the libs, then > > what is the correct course of action to properly > > install the bind8 port into a system? > > > > Many thanks, Byron > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38062661.AFD4141>