From owner-freebsd-questions@FreeBSD.ORG Tue May 25 02:40:19 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 605B21065670 for ; Tue, 25 May 2010 02:40:19 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [76.96.27.227]) by mx1.freebsd.org (Postfix) with ESMTP id 41A9D8FC14 for ; Tue, 25 May 2010 02:40:19 +0000 (UTC) Received: from omta02.emeryville.ca.mail.comcast.net ([76.96.30.19]) by qmta12.emeryville.ca.mail.comcast.net with comcast id McKN1e0090QkzPwACegK8J; Tue, 25 May 2010 02:40:19 +0000 Received: from comcast.net ([98.203.142.76]) by omta02.emeryville.ca.mail.comcast.net with comcast id MegJ1e0041f6R9u8NegJ7z; Tue, 25 May 2010 02:40:19 +0000 Received: by comcast.net (sSMTP sendmail emulation); Mon, 24 May 2010 19:40:16 -0700 Date: Mon, 24 May 2010 19:40:16 -0700 From: Charlie Kester To: freebsd-questions@freebsd.org Message-ID: <20100525024015.GG216@comcast.net> Mail-Followup-To: freebsd-questions@freebsd.org, ler@lerctr.org References: <44y6f8g30c.fsf@lowell-desk.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <44y6f8g30c.fsf@lowell-desk.lan> X-Mailer: Mutt 1.5.20 X-Composer: Vim 7.2 User-Agent: Mutt/1.5.20 (2009-06-14) Cc: ler@lerctr.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 02:40:19 -0000 On Mon 24 May 2010 at 18:54:11 PDT Lowell Gilbert wrote: >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. Since we're talking about building a port, you should also involve its maintainer. I've cc'ed him with this reply. I just tried building lsof myself, on a 686-class 8.0-STABLE machine, and had the same successful result as Lowell. Can you give us a copy of the build output, beginning with the cc command line that immediately precedes the failure?