From owner-freebsd-current@FreeBSD.ORG Mon Apr 7 04:18:44 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 1C90F37B401 for ; Mon, 7 Apr 2003 04:18:44 -0700 (PDT) Received: from k6.locore.ca (k6.locore.ca [198.96.117.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EF2743FA3 for ; Mon, 7 Apr 2003 04:18:43 -0700 (PDT) (envelope-from jake@k6.locore.ca) Received: from k6.locore.ca (localhost.locore.ca [127.0.0.1]) by k6.locore.ca (8.12.8/8.12.8) with ESMTP id h37BIoxS074710; Mon, 7 Apr 2003 07:18:50 -0400 (EDT) (envelope-from jake@k6.locore.ca) Received: (from jake@localhost) by k6.locore.ca (8.12.8/8.12.8/Submit) id h37BIoQR074709; Mon, 7 Apr 2003 07:18:50 -0400 (EDT) Date: Mon, 7 Apr 2003 07:18:50 -0400 From: Jake Burkholder To: Kris Kennaway Message-ID: <20030407111850.GC67830@locore.ca> References: <20030407103501.GM56702@rot13.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030407103501.GM56702@rot13.obsecurity.org> User-Agent: Mutt/1.4i cc: current@FreeBSD.org Subject: Re: vm_paddr_t causing port errors 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: Mon, 07 Apr 2003 11:18:44 -0000 Apparently, On Mon, Apr 07, 2003 at 03:35:01AM -0700, Kris Kennaway said words to the effect of; > It looks like a number of ports are failing on alpha with an error > relating to vm_paddr_t. Can whoever is responsible please > investigate? > > http://bento.freebsd.org/errorlogs/alpha-5-latest/ezload-0.3.1.log > http://bento.freebsd.org/errorlogs/alpha-5-latest/lsof-4.67.log > http://bento.freebsd.org/errorlogs/alpha-5-latest/tircproxy-0.4.5_3.log It looks like these ports include kernel headers directly from a source tree, not from the installed includes. This will not work unless your world is up to date. Please don't blame kernel developers for broken applications. Jake