Date: Tue, 14 Apr 2015 10:12:05 -0400 (EDT) From: "Stephen Roznowski" <sjroz@verizon.net> To: portmgr-feedback@FreeBSD.org Cc: ports@FreeBSD.org, bapt@freebsd.org Subject: Re: FreeBSD ports which are currently marked broken Message-ID: <0NMS000L7VG60L30@vms173021.mailsrvcs.net> In-Reply-To: <201504070829.t378TVCu012077@portsmon.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This port (and probably others) is broken because MASTER_SITE_COMP_SOURCES doesn't have a working mirror. I also see that MASTER_SITE_COMP_SOURCES has been removed from Mk/bsd.sites.mk. A quick seach shows the following sites still hosting comp.sources, are any of these acceptable to use as the master sites? http://ftp.sunet.se/pub/usenet/ftp.uu.net/comp.sources.unix/ http://ftp.isc.org/pub/usenet/comp.sources.unix/ http://ftp.funet.fi/pub/archive/comp.sources.unix/ http://ftp.fi.netbsd.org/pub/misc/archive/comp.sources.unix/ Thanks, -SR On 7 Apr, linimon@FreeBSD.org wrote: > As part of an ongoing effort to reduce the number of problems in > the FreeBSD ports system, we periodically notify users of ports > that are marked as "broken" in their Makefiles. In many cases > these ports are failing to compile on some subset of the FreeBSD > build environments. One common problem is that recent versions of > FreeBSD use clang instead of gcc by default. Another common problem > is that the compiles succeed on the i386 and amd64 architecture > (e.g. the common Intel PC), but fail on one or more of the other > architectures due to assumptions about things such as size of various > types, byte-alignment issues, and so forth. > > In occasional cases we see that the same port may have different > errors in different build environments. The script that runs on the > build cluster uses heuristics to try to 'guess' the error type to > help you isolate problems, but it is only a rough guide. > > One more note: on occasion, there are transient build errors seen > on the build farm. Unfortunately, there is not yet any way for this > algorithm to tell the difference (humans are much, much better at > this kind of thing.) > > The errors are listed below. In the case where the same problem > exists on more than one build environment, the URL points to the > latest errorlog for that type. (By 'build environment' here we > mean 'combination of 8.x/9.x/10.x/-current with target architecture'.) > > [snip] > > portname: sysutils/copytape > broken because: No public distfiles > build errors: none. > overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=copytape -- Stephen J. Roznowski (sjroz@verizon.net)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0NMS000L7VG60L30>