Date: Wed, 9 Jun 2004 08:15:22 -0400 From: Bill Moran <wmoran@potentialtech.com> To: Edd <list@arameus.net> Cc: freebsd-questions@freebsd.org Subject: Re: I must be doing something wrong! Message-ID: <20040609081522.34cf5eaf.wmoran@potentialtech.com> In-Reply-To: <200406091203.i59C31b25411@server1.web-mania.com> References: <200406091055.QAA08622@manage.24online> <200406091203.i59C31b25411@server1.web-mania.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Edd <list@arameus.net> wrote: > > Tryed this and it did not work :( > > Thinking about it profiled libs are not even a part of a kernel. > > /usr/src/sys/geom/geom_io.c: In function `g_io_request': > /usr/src/sys/geom/geom_io.c:283: structure has no member named `wentbusy' > /usr/src/sys/geom/geom_io.c:285: structure has no member named `wentbusy' > /usr/src/sys/geom/geom_io.c: In function `g_io_deliver': > /usr/src/sys/geom/geom_io.c:330: structure has no member named `updating' > /usr/src/sys/geom/geom_io.c:331: structure has no member named `updating' > /usr/src/sys/geom/geom_io.c:354: structure has no member named `wentbusy' > /usr/src/sys/geom/geom_io.c:355: structure has no member named `bt' > /usr/src/sys/geom/geom_io.c:356: structure has no member named `wentbusy' > /usr/src/sys/geom/geom_io.c:359: structure has no member named `wentbusy' > /usr/src/sys/geom/geom_io.c:360: structure has no member named `bt' > /usr/src/sys/geom/geom_io.c:361: structure has no member named `wentbusy' > /usr/src/sys/geom/geom_io.c:363: structure has no member named `updating' > /usr/src/sys/geom/geom_io.c:364: structure has no member named `updating' > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/HITBOX. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > Can you just catch the tree at a bad time when it will not compile? Yes, it's not unusual at all with -CURRENT. If you're going to run -CURRENT, you should subscribe to the -CURRENT mailing list. There's usually heads-ups called if someone expects to break the tree, and usually a lot of discussion when the tree is broken. If lurking on the -CURRENT list for a while doesn't reveal the nature of the problem, post the errors you're getting to -CURRENT, and I'm sure someone will have reasonable advice for you. It also wouldn't be unusual if the breakage is already fixed and you just need to cvsup again. Good luck. -- Bill Moran Potential Technologies http://www.potentialtech.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040609081522.34cf5eaf.wmoran>