From owner-freebsd-questions@FreeBSD.ORG Tue May 25 01:54:21 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF178106564A for ; Tue, 25 May 2010 01:54:21 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail5.sea5.speakeasy.net (mail5.sea5.speakeasy.net [69.17.117.49]) by mx1.freebsd.org (Postfix) with ESMTP id A6A288FC0A for ; Tue, 25 May 2010 01:54:21 +0000 (UTC) Received: (qmail 12668 invoked from network); 25 May 2010 01:54:20 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail5.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 25 May 2010 01:54:20 -0000 Received: from lowell-desk.lan (lowell-desk.lan [172.30.250.6]) by be-well.ilk.org (Postfix) with ESMTP id B1B7E5082A; Mon, 24 May 2010 21:54:13 -0400 (EDT) Received: by lowell-desk.lan (Postfix, from userid 1147) id B201A1CCA3; Mon, 24 May 2010 21:54:11 -0400 (EDT) From: Lowell Gilbert To: Arthur Barlow References: Date: Mon, 24 May 2010 21:54:11 -0400 In-Reply-To: (Arthur Barlow's message of "Mon, 24 May 2010 17:41:21 -0700") Message-ID: <44y6f8g30c.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: Problem compiling lsof X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 May 2010 01:54:21 -0000 Arthur Barlow writes: > Sorry about the false start. Fat fingers. I'm trying to compile the lsof > program in FreeBSD 8.0 on an i686 machine. There is a error referencing > "dlsof.h" and it looks like there is an ugly "hack" in the header file. Any > suggestions, besides playing with the code? As of a few minutes ago, it built just fine on my i386 build system with the latest ports. If you want help diagnosing your issue, you will need to be much more specific about what happens on your particular system, so we can figure out how it differs from a normal system.