Date: Sat, 6 May 2000 06:12:08 -0700 (PDT) From: "J. Goodleaf" <goodleaf@home.com> To: Salvo Bartolotta <bartequi@neomedia.it> Cc: questions@freebsd.org Subject: Re: Help! make installworld error; addendum to Asante NIC Message-ID: <Pine.BSF.4.21.0005060603210.19655-100000@C702312-A.sttln1.wa.home.com> In-Reply-To: <20000505.16591100@bartequi.ottodomain.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for your help. Per your (and Sheldon's) suggestions, the make -DNOINFO installworld worked fine. But it's still a little confusing. I've been on Freebsd 4 for a while. I started from scratch too, so this particular machine has never had anything but v4 on it. I successfully CVSup'd and used make buildworld & installworld previously. So it is not clear to me why I developed a problem that should be seen by upgraders from 3.4. (It had never occurred to me to look in the UPDATING file for this reason.) Could it be related to ports? Since the previous success, I've installed a slew of ports (which have also been cvsup'd) relating to Gnome, the text editor, the calendar etc. Not much else though. Hypotheses? -J On Fri, 5 May 2000, Salvo Bartolotta wrote: > >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< > > On 5/5/00, 4:24:18 AM, "J. Goodleaf" <goodleaf@seanet.com> wrote > regarding Help! make installworld error; addendum to Asante NIC: > > > > Have CVSup'd (How do you pronounce that?) twice in the last week. Each > > time the make buildworld procedure works perfectly, but make > installworld > > generates the following error message (abstracted from the end of the > > installworld output). > > > What should I do now? (This is 4_STABLE) > > > Also, I asked question about an Asante 10/100 Mac-PC NIC earlier > > this week. Thanks for your suggestions. The final answer was: > > It works, using the dc device. However, it is consistently slower > > than my 3Com 905 TXs. Hmmm. > > > Thanks in advance, > > John > > > ===> lib/libcom_err > > cd /usr/src/lib/libcom_err && install -C -o root -g wheel -m 444 > > /usr/src/lib/libcom_err/../../contrib/com_err/com_err.h /usr/include > > cd /usr/src/lib/libcom_err && install -C -o root -g wheel -m 444 > > /usr/src/lib/libcom_err/../../contrib/com_err/com_right.h /usr/include > > install -c -o root -g wheel -m 444 libcom_err.a /usr/lib > > install -c -o root -g wheel -m 444 libcom_err_p.a /usr/lib > > install -c -s -o root -g wheel -m 444 libcom_err.so.2 /usr/lib > > ln -sf libcom_err.so.2 /usr/lib/libcom_err.so > > install -c -o root -g wheel -m 444 com_err.3.gz /usr/share/man/man3 > > ===> lib/libcom_err/doc > > install-info --quiet --defsection="Programming & development > > tools." --defentry="* libcom_err: (com_err). A Common Error > > Description Library for UNIX." com_err.info /usr/share/info/dir > > *** Error code 1 > > > Stop in /usr/src/lib/libcom_err/doc. > > *** Error code 1 > > > Stop in /usr/src/lib/libcom_err. > > *** Error code 1 > > > Stop in /usr/src/lib. > > *** Error code 1 > > > Stop in /usr/src. > > *** Error code 1 > > > Stop in /usr/src. > > *** Error code 1 > > > Stop in /usr/src. > > *** Error code 1 > > > Stop in /usr/src. > > > > Dear J. Goodleaf, > > I may be wrong, but I recall meeting this error when I upgraded from > 3.4-S to 4.0-S for the first time. > > You might apply the same workaround, which should still be described > in /usr/src/UPDATING: i.e. you might first install the world with the > -DNOINFO option. Also, the -k option might be necessary, too. > > It's a couple of weeks since I last made the world for my 4.0-S > system. I'll check this personally in a while, probably adding to your > woes :-) > > Good luck, > Salvo > > > > > 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?Pine.BSF.4.21.0005060603210.19655-100000>