Date: Fri, 20 May 2005 09:54:21 -0700 From: Ade Lovett <ade@FreeBSD.org> To: Frederick K.Horman <fredh@the-mcdonalds.org> Cc: ports@FreeBSD.org Subject: Re: FreeBSD Port: gmake-3.80_2 Message-ID: <A658A241-32A5-4E42-8988-13D27519C524@FreeBSD.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A658A241-32A5-4E42-8988-13D27519C524>