Date: Tue, 7 Feb 1995 17:13:30 -0600 (CST) From: "Clay D. Hopperdietzel" <hoppy@appsmiths.com> To: hackers@FreeBSD.org Subject: more 2.0-950202 build fun Message-ID: <199502072313.RAA26198@anvil.appsmiths.com>
next in thread | raw e-mail | index | archive | help
More stuff on building 950202-SNAP:
(Ignore the zaney symlinks)
===> usr.bin/tn3270/tn3270
cd /u2/freebsd200/950202/src/usr.bin/tn3270/tn3270/../tools/mkastosc; make
cc -O2 -I/u2/freebsd200/950202/src/usr.bin/tn3270/tools/mkastosc/../mkhits -I/u2/freebsd200/950202/src/usr.bin/tn3270/tools/mkastosc/.. -I. -o mkastosc mkastosc.o dohits.o asc_ebc.o ebc_disp.o
/u2/freebsd200/950202/src/usr.bin/tn3270/tn3270/../tools/mkastosc/obj/mkastosc /u2/freebsd200/950202/src/usr.bin/tn3270/tn3270/../ctlr/hostctlr.h /u2/freebsd200/950202/src/usr.bin/tn3270/tn3270/../ctlr/function.h < /u2/freebsd200/950202/src/usr.bin/tn3270/tn3270/../ctlr/unix.kbd > astosc.OUT
/u2/freebsd200/950202/src/usr.bin/tn3270/tn3270/../tools/mkastosc/obj/mkastosc: not found
*** Error code 2 (continuing)
[.. more of this ..]
[...]
===> usr.sbin/lsdev
cc -O2 -I/u2/freebsd200/950202/src/usr.sbin/lsdev/../../sys -c i386.c
i386.c: In function `print_config':
i386.c:49: `PCI_EXTERNAL_LEN' undeclared (first use this function)
i386.c:49: (Each undeclared identifier is reported only once
i386.c:49: for each function it appears in.)
i386.c: In function `print_pci':
i386.c:173: dereferencing pointer to incomplete type
i386.c:174: dereferencing pointer to incomplete type
i386.c:182: dereferencing pointer to incomplete type
*** Error code 1
Stop.
*** Error code 1 (continuing)
------------------------------------------------------------------------------
Also, I started running it. I mean *running it*. Fired up X, started a
g++ compile which eventually eats > 50MB of virtual on a 16MB machine.
FreeBSD does a *whole* lot better than HP/UX at this trick, however, I was
banging around on some other windows, and *woof* out to the BIOS warm-boot.
No panic, nothing. Haven't repeated it, but its been hours, not days.
Also, and I've had this trouble since I first started with 2.X, is that
while in X11, I eventually get some processes to keel over in such
a way as I have to reboot the system to shake them. In this particular
case, I folded up 'X11' and did a 'kill 1' to get back to '-s' mode:
ps gives:
UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND
0 310 1 5 -18 0 316 1416 vodead D p1- 0:00.24 xterm
0 312 1 10 -18 0 316 1404 vodead D+ p1- 0:00.24 xterm
100 272 1 47 -18 0 468 12 objtrm D p3- 0:05.48 tar xvzf gcc-
100 273 272 3 28 0 0 0 - Z p3- 0:00.00 (gzip)
0 298 1 19 -18 0 344 1380 vodead D v0- 0:00.30 xterm -name x
0 300 1 21 -18 0 344 1424 vodead D v0- 0:00.27 xterm -name x
0 342 1 0 10 0 448 296 wait Ss ?? 0:00.16 -sh (sh)
0 354 342 3 28 0 416 224 - R+ ?? 0:00.01 ps -al
the tar/gzip pair were running in a window at the time, along with the
afformentioned 'fat' compile, which has since evaporated.
I've observed that once you reach this point, you cannot start anymore
X11 based things (like xterms) but can use windows which are still alive.
If somebody wants me to do something (besides shut-up) to help with these,
speak up.
===============================================================================
Clay D. Hopperdietzel hoppy@appsmiths.com
AppSmiths, Inc. (713) 578-0154
Houston, Texas USA Happiness is OG > 1.0500
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199502072313.RAA26198>