Date: Mon, 7 Oct 2013 08:28:21 GMT From: linimon@FreeBSD.org To: ruby@freebsd.org Subject: FreeBSD ports that you maintain which are currently marked broken Message-ID: <201310070828.r978SLKQ051690@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. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 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 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: audio/ruby-vorbisfile broken because: does not compile with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ruby-vorbisfile portname: audio/ruby-xmms broken because: does not compile with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ruby-xmms portname: databases/rubygem-delayed_job_data_mapper broken because: delayed_job_data_mapper requires delayed_job (~> 2.1) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=rubygem-delayed_job_data_mapper portname: devel/ruby-fam broken because: does not build with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ruby-fam portname: devel/ruby-io-reactor broken because: does not build with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ruby-io-reactor portname: devel/ruby-jttui broken because: does not build with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ruby-jttui portname: devel/ruby-racc broken because: Builds but does not work with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ruby-racc portname: devel/ruby-slang broken because: does not build with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ruby-slang portname: devel/rubygem-linecache broken because: does not work with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=rubygem-linecache portname: devel/rubygem-ncurses broken because: does not work with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=rubygem-ncurses portname: devel/rubygem-parsetree broken because: Builds with ruby 1.9, but does not work with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=rubygem-parsetree portname: devel/rubygem-rparsec broken because: does not work with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=rubygem-rparsec portname: devel/rubygem-sdl broken because: does not work with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=rubygem-sdl portname: games/ruby-exmars broken because: does not build with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=ruby-exmars portname: graphics/ruby-opengl broken because: does not build with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=ruby-opengl portname: graphics/ruby-pgplot broken because: does not build with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=ruby-pgplot portname: graphics/rubygem-turing broken because: does not work with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=rubygem-turing portname: japanese/ruby-chasen broken because: does not build with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=ruby-chasen portname: japanese/ruby-slang broken because: does not build with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=ruby-slang portname: lang/ruby-lua4 broken because: does not build with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=ruby-lua4 portname: sysutils/rubygem-chef-expander broken because: fails to install build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.9.20131001065611.pointyhat/rubygem-chef-expander-10.24.0.log (Sep 2 12:14:37 UTC 2013) overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=rubygem-chef-expander portname: sysutils/rubygem-chef-solr broken because: fails to install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=rubygem-chef-solr portname: textproc/ruby-amrita broken because: does not build with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=ruby-amrita portname: textproc/ruby-xmlscan-old broken because: does not build with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=ruby-xmlscan-old portname: textproc/rubygem-htmltools broken because: does not work with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=rubygem-htmltools portname: www/rubygem-mongrel broken because: does not work with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=rubygem-mongrel portname: x11-toolkits/ruby-gtk broken because: does not build with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=ruby-gtk portname: x11-toolkits/ruby-tk broken because: does not build with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=ruby-tk portname: x11/ruby-gtktrayicon broken because: does not build with ruby 1.9 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=ruby-gtktrayicon 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?201310070828.r978SLKQ051690>