Date: Mon, 11 Oct 1999 14:43:36 +0000 From: freebsd@mrynet.com (FreeBSD mailing list) To: freebsd-current@freebsd.org Subject: World fail + resulting cvsup failures Message-ID: <199910112143.OAA08646@mrynet.com>
next in thread | raw e-mail | index | archive | help
After an attempt to build world failed early this morning after a
cvsup, I can neither resolve the world problem, nor can I cvsup.
World failure:
===> usr.bin/kdump
cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../..
-I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/kdump/kdump.c
/bin/sh /usr/src/usr.bin/kdump/mkioctls > ioctl.c
In file included from :45:
/usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE'
redefined
/usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the
location of the previous definition
cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../..
-I/usr/obj/usr/src/tmp/usr/include -c ioctl.c
In file included from ioctl.c:65:
/usr/obj/usr/src/tmp/usr/include/sys/memrange.h:16: warning: `MDF_ACTIVE'
redefined
/usr/obj/usr/src/tmp/usr/include/pccard/cardinfo.h:77: warning: this is the
location of the previous definition
ioctl.c: In function `ioctlname':
ioctl.c:353: sizeof applied to an incomplete type
ioctl.c:617: sizeof applied to an incomplete type
*** Error code 1
Stop in /usr/src/usr.bin/kdump.
*** Error code 1
Now, certainly this is unrelated to cvsup failing, however something
else in the build must have caused the following:
mrynet# cvsup
***
*** runtime error:
*** Segmentation violation - possible attempt to dereference NIL
*** pc = 0x2f
***
Abort trap
A reboot has effected no change in this behavior.
An attempt to reinstall modula from ports results in:
---------------------- building m3core ----------------------
mkdir FreeBSD2
--- building in FreeBSD2 ---
m3 -w1 -why -O -times -a libm3core.a -F/var/tmp/qkAK8630
***
*** runtime error:
*** Segmentation violation - possible attempt to dereference NIL
*** pc = 0x2f
***
Abort trap
*** error code 134 (ignored)
So, the problem lies in Modula 3.
I'm at a total stalemate now. Has anyone experienced this? All
(constructive :P) suggestions hearily welcomed :D
Cheers,
-skots
--
Scott G. Akmentins-Taylor InterNet: staylor@mrynet.com
MRY Systems staylor@mrynet.lv
(Skots Gregorijs Akmentins-Teilors -- just call me "Skots")
----- Labak miris neka sarkans -----
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199910112143.OAA08646>