Date: Wed, 11 Apr 2001 17:07:19 -0700 (PDT) From: David Wolfskill <david@catwhisker.org> To: bp@butya.kz, david@catwhisker.org Cc: current@FreeBSD.ORG Subject: Re: world (still) having trouble (after gdb.291/gdb/defs.h) Message-ID: <200104120007.f3C07JN67377@bunrab.catwhisker.org> In-Reply-To: <Pine.BSF.4.21.0104120438120.4856-100000@lion.butya.kz>
next in thread | previous in thread | raw e-mail | index | archive | help
>Date: Thu, 12 Apr 2001 04:40:03 +0700 (ALMST) >From: Boris Popov <bp@butya.kz> >> In "stage 4: building everything...", it got well past that point, but >> blew up in usr.bin/kdump: > Sorry, delta was committed to smb_dev.h. It should be ok now. Yup -- built; I'm running: FreeBSD m133.whistle.com 5.0-CURRENT FreeBSD 5.0-CURRENT #26: Wed Apr 11 09:36:48 PDT 2001 root@:/common/C/obj/usr/src/sys/LAPTOP_30W i386 (in multi-user mode) right now. Thanks! That said, while I was trying to figure out what had gone wrong, I ended up chasing something that was "merely" a warning, but loks to me as if it has some unpleasant potential: the dual (conflicting) definitions of MDF_ACTIVE, thus: sys/pccard/cardinfo.h:81:#define MDF_ACTIVE 0x40 /* Context active (read-only) */ and sys/sys/memrange.h:18:#define MDF_ACTIVE (1<<27) /* currently active */ The notion of the same program (kdump, in this case) actually using both include files would seem to be a cause for some concern. Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. 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?200104120007.f3C07JN67377>