Date: Sun, 7 Dec 1997 17:48:51 -0800 (PST) From: Doug White <dwhite@gdi.uoregon.edu> To: Barry Masterson <jbarrm@panix.com> Cc: FreeBSD-questions <questions@FreeBSD.ORG> Subject: Re: Dealing with "BROKEN" (pgcc) ports Message-ID: <Pine.BSF.3.96.971207174816.11954K-100000@gdi.uoregon.edu> In-Reply-To: <Pine.SUN.3.94.971205223223.1866A-100000@panix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 5 Dec 1997, Barry Masterson wrote: > I'm attempting to build pgcc from the 2.2.5 CD. I have the > source for gcc-2.7.2.tar.gz (with matching checksums, not easy > to find), and have encountered the line during 'make': > > "pgcc-2.7.2.9 is marked as broken: patching dosen't work, PLIST > untested" > > My question; how do I deal with the "BROKEN" line that is listed > in the Makefile? You fix what's broken. Sounds like the patches are out of date. pgcc is also known to generate broken code. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.971207174816.11954K-100000>