From owner-freebsd-current@FreeBSD.ORG Mon Apr 21 21:12:22 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 7567937B404 for ; Mon, 21 Apr 2003 21:12:22 -0700 (PDT) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0201B43FF5 for ; Mon, 21 Apr 2003 21:12:22 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0085.cvx40-bradley.dialup.earthlink.net ([216.244.42.85] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 197p8j-0001Nt-00; Mon, 21 Apr 2003 21:12:18 -0700 Message-ID: <3EA4C0D3.8F7CF9EE@mindspring.com> Date: Mon, 21 Apr 2003 21:10:59 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: leafy References: <20030422031429.GA82023@chihiro.leafy.idv.tw> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4a0d841dab08150fde455fa64d7fb04d0350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c 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 04:12:22 -0000 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. -- Terry