From owner-freebsd-current@FreeBSD.ORG Tue Apr 22 11:24:25 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A201937B401 for ; Tue, 22 Apr 2003 11:24:25 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77DB343FA3 for ; Tue, 22 Apr 2003 11:24:24 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id EAA01815; Wed, 23 Apr 2003 04:24:14 +1000 Date: Wed, 23 Apr 2003 04:24:12 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Terry Lambert In-Reply-To: <3EA4C0D3.8F7CF9EE@mindspring.com> Message-ID: <20030423041754.N18663@gamplex.bde.org> References: <20030422031429.GA82023@chihiro.leafy.idv.tw> <3EA4C0D3.8F7CF9EE@mindspring.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: leafy cc: freebsd-current@freebsd.org Subject: Re: Is there a header conflict? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Apr 2003 18:24:25 -0000 On Mon, 21 Apr 2003, Terry Lambert wrote: > leafy wrote: > > While compiling net-snmp port, I came across this error > > > > rm -f host/.libs/hr_storage.lo > > cc -I../../include -I../../include -I. -I../.. -I. -I./../.. -I./../../snmplib - > > I./.. -I.. -DINET6 -O -pipe -mcpu=pentiumpro -Dfreebsd5 -c host/hr_storage.c -f > > PIC -DPIC -o host/.libs/hr_storage.lo > > In file included from host/hr_storage.c:36: > > /usr/include/machine/types.h:50: redefinition of `vm_offset_t' > > /usr/include/sys/types.h:250: `vm_offset_t' previously declared here > [ ... ] > > Is this a header conflict? > > No, this is broken source code. > > User programs should not reference the "machine" headers directly. Also, including should fail earlier because this header shouldn't exist. It was renamed to in -current to inhibit direct inclusion of it. Bruce