Date: Tue, 21 Apr 2015 08:29:07 GMT From: linimon@FreeBSD.org To: ruby@freebsd.org Subject: FreeBSD ports that you maintain which are currently marked broken Message-ID: <201504210829.t3L8T7GJ091243@portsmon.freebsd.org>
next in thread | raw e-mail | index | archive | help
Dear FreeBSD port maintainer: 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'.) portname: archivers/ruby-zip broken because: Does not build with Ruby 2.1 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=ruby-zip portname: audio/ruby-audiofile broken because: Unfetchable build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ruby-audiofile portname: audio/ruby-mp3tag broken because: Unfetchable build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ruby-mp3tag portname: databases/rubygem-bdb1 broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=rubygem-bdb1 portname: databases/rubygem-memcache broken because: Does not build with Ruby 2.1 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=rubygem-memcache portname: devel/rubygem-igraph broken because: does not build with igraph-0.7.1 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=rubygem-igraph portname: graphics/rubyphoto broken because: No public distfiles build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=rubyphoto If these errors are ones that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Every effort has been made to make sure that these error reports really do correspond to a port that you maintain. However, due to the fact that this is an automated process, it may indeed generate false matches. If one of these errors fits that description, please forward this email to the author of this software, Mark Linimon <linimon@FreeBSD.org>, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201504210829.t3L8T7GJ091243>