Re: world (still) having trouble (after gdb.291/gdb/defs.h)
In message [EMAIL PROTECTED] David Wolfskill writes: : 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 (127) /* 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. Don't worry about it. The person who imported the memcontrol stuff didn't check the system closely enough for conflicts. The pccard define has been around since 1996 while the memcontrol one was added in 1999 and still hasn't been fixed :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: world (still) having trouble (after gdb.291/gdb/defs.h)
On Fri, 20 Apr 2001, Warner Losh wrote: In message [EMAIL PROTECTED] David Wolfskill writes: : The notion of the same program (kdump, in this case) actually using both : include files would seem to be a cause for some concern. Don't worry about it. The person who imported the memcontrol stuff didn't check the system closely enough for conflicts. The pccard define has been around since 1996 while the memcontrol one was added in 1999 and still hasn't been fixed :-) Building with "mkioctls -s" also shows many conflicting numeric ioctl values (probably many more than in 1996). This is mostly another non- problem, since the conflicting values mostly go to different drivers, but it prevents utilities like kdump from interpreting ioctl numbers unambiguously. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: world (still) having trouble (after gdb.291/gdb/defs.h)
On Wed, 11 Apr 2001, David Wolfskill wrote: 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. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: world (still) having trouble (after gdb.291/gdb/defs.h)
Date: Thu, 12 Apr 2001 04:40:03 +0700 (ALMST) From: Boris Popov [EMAIL PROTECTED] 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 (127) /* 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
