From owner-freebsd-ports@FreeBSD.ORG Fri May 20 16:54:25 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC6B016A4CE for ; Fri, 20 May 2005 16:54:25 +0000 (GMT) Received: from mail.lovett.com (foo.lovett.com [67.134.38.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7173943D9F for ; Fri, 20 May 2005 16:54:25 +0000 (GMT) (envelope-from ade@FreeBSD.org) Received: from hellfire.lovett.com ([67.134.38.149]) by mail.lovett.com with esmtpa (Exim 4.51 (FreeBSD)) id 1DZAlG-0001Pu-2m; Fri, 20 May 2005 09:54:10 -0700 In-Reply-To: <6.2.0.14.2.20050520053839.01efcd00@ubox.the-mcdonalds.org> References: <6.2.0.14.2.20050520053839.01efcd00@ubox.the-mcdonalds.org> Mime-Version: 1.0 (Apple Message framework v730) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Ade Lovett Date: Fri, 20 May 2005 09:54:21 -0700 To: Frederick K.Horman X-Mailer: Apple Mail (2.730) cc: ports@FreeBSD.org Subject: Re: FreeBSD Port: gmake-3.80_2 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2005 16:54:26 -0000 On May 20, 2005, at 02:39 , Frederick K. Horman wrote: > In FreeBSD 4.11 gmake 3.80_@ no longer compiles, It may not compile *for you*, but it most certainly compiles and builds on clean systems, for example: http://pointyhat.freebsd.org/errorlogs/i386-4-latest-logs/ gmake-3.80_2.log (this was from a mere few hours ago it looks like). > it stops with the following errors. > > arscan.c: In function `ar_scan': > arscan.c:386: `ARMAG' undeclared (first use in this function) Poking into the code, it would appear that the only way that this could not get defined (modulo the system being completely hosed) is if you have an "ar.h" header file floating around in /usr/local/ include installed by another port. Of course, you snipped out the actual compilation command from the build log, which really doesn't help matters. Remember, gmake is one of those subset of ports that a LOT of other ports depend on to be built. If there were some kind of generalized failure, I have no doubt that the ports@ mailing lists would be quickly carpet-bombed by complaints. Given that there are currently no craters in the vicinity of this mailing list, the problem is likely to be more specific to your system. -aDe