So I tried make clean, and reran make buildworld.
Its still failing in the same spot ->
/usr/libexec/elf/ld: cannot find -ltermcap
*** Error code 1
Stop in /usr/src/gnu/usr.bin/texinfo/info.
*** Error code 1
Stop in /usr/src/gnu/usr.bin/texinfo.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
gatekeeper#
Marc Silver wrote:
Hi there,
Did you clean out /usr/obj before you started the 'make buildworld'??
If you have previously compiled buildworld, then this is something you
should do. To do this:
cd /usr/obj
chflags -R noschg *
rm -fr /usr/obj/usr
Then, 'make clean' in /usr/src and start again. Hopefully that'll fix
it.
- Marc
On Tue, Feb 04, 2003 at 12:37:24AM -0500, Gerard Samuel wrote:
I have a FreeBSD 4.7 p2 box, and Im trying to upgrade to p3.
I just did a fresh cvsup, and cd to /usr/src
Execute make buildworld, and its failing at ->
cc -O -pipe -DINFODIR=\"/usr/share/info:/usr/local/info:/usr/X11R6/info:.\" -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/info/../../../../contrib/texinfo -I/usr/src/gnu/usr.bin/texinfo/info/../../../../contrib/texinfo/lib -D__FBSDID=__RCSID -static -o info dir.o display.o doc.o dribble.o echo-area.o filesys.o footnotes.o gc.o indices.o info-utils.o info.o infodoc.o infomap.o m-x.o man.o nodemenu.o nodes.o search.o session.o signals.o terminal.o tilde.o variables.o window.o -ltermcap /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/texinfo/info/../libtxi/libtxi.a
/usr/libexec/elf/ld: cannot find -ltermcap
*** Error code 1
Stop in /usr/src/gnu/usr.bin/texinfo/info.
*** Error code 1
Stop in /usr/src/gnu/usr.bin/texinfo.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
gatekeeper#
Any ideas what I can do to recitify this problem.
Thanks.
--
Gerard Samuel
http://www.trini0.org:81/
http://dev.trini0.org:81/
-- Gerard Samuel http://www.trini0.org:81/ http://dev.trini0.org:81/
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
