From owner-freebsd-questions@FreeBSD.ORG Thu Apr 22 06:54:39 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F15616A4CE for ; Thu, 22 Apr 2004 06:54:39 -0700 (PDT) Received: from auemail1.firewall.lucent.com (auemail1.lucent.com [192.11.223.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB9BE43D53 for ; Thu, 22 Apr 2004 06:54:38 -0700 (PDT) (envelope-from shawnlkennedy@lucent.com) Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70]) ESMTP id i3MDsXj20781 for ; Thu, 22 Apr 2004 08:54:34 -0500 (CDT) Received: from il0015shawnlke2 (il0015shawnlke2.ih.lucent.com [135.185.54.213]) by ihmail.ih.lucent.com (8.11.7+Sun/EMS-1.5 sol2) id i3MDsWR28101; Thu, 22 Apr 2004 08:54:32 -0500 (CDT) From: "Shawn Kennedy" To: Date: Thu, 22 Apr 2004 08:54:33 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal In-Reply-To: <20040421221655.GA85479@xor.obsecurity.org> Subject: RE: PORT comms/gnokii won't build X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: shawnlkennedy@lucent.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Apr 2004 13:54:39 -0000 > -----Original Message----- > From: Kris Kennaway [mailto:kris@obsecurity.org] > Sent: Wednesday, April 21, 2004 5:17 PM > To: Shawn Kennedy > Cc: freebsd-questions@FreeBSD.org > Subject: Re: PORT comms/gnokii won't build > > > On Wed, Apr 21, 2004 at 12:35:04PM -0500, Shawn Kennedy wrote: > > > > A port update came in for gnokii and I can't get it > > to build. It's trying to use stdint.h even though > > it checks for it and cannot find it (finds inttypes.h > > which is correct). Below is the offending > > portion of the build. Anyone with > > any ideas? > > Talk to the port maintainer, or complain to the software developers > for writing unportable code. FYI - I was able to get a hold of the port owner - they found the problem and submitted changes via CVS last night. Shawn