Hello Dear
G3TUP 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 google it 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: devel/hyena broken because: Does not build with recent mono build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=hyena 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 Hotmail or Outlook 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 , so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. October 22, 2018 Deutsche Bank's ESG Investing Conference 2018 showcases bank's growth in sustainable business expertise August 2, 2018 Deutsche Bank joins Pearl Jam, the Bill & Melinda Gates Foundation and the Raikes Foundation to battle homelessness June 1, 2018 2018 June Pride Month: dbPride schedule of events May 29, 2018 WOWS hosts inaugural speed networking event March 16, 2018 Tom Patrick accepts Deutsche Bank's 2018 StreetWise Partners Champion Award Corporate & Investment Banking DWS Insights Strategies Solutions Our clients Global Markets Private, Wealth & Commercial Clients Notice: By federal law, as of 1/1/2013, funds in a noninterest-bearing transaction account (including an IOLTA/IOLA) will no longer receive unlimited deposit insurance coverage, but will be FDIC-insured to the legal maximum of $250,000 for each ownership category. For more information visit: www.fdic.gov/deposit/deposits/unlimited/expiration.html