FW: FreeBSD ports that you maintain which are currently marked broken

Pietro Cerutti gahr at gahr.ch
Wed Oct 29 19:47:46 UTC 2014

Hi apache@,

can anybody help Jeff figure out what's going on? I know the default
apache version has changed from 2.2 to 2.4, but I'm pretty much afk at
the moment and haven't followed closely..


On 2014-Oct-29, 18:43, Jeff Lawson wrote:
> Pietro,
> Can you look into this breakage of the mod_rivet port? I'm not sure what
> the issue is.
> Thanks,
> Jeff
> On 10/21/14, 3:28 AM, "linimon at FreeBSD.org" <linimon at FreeBSD.org> wrote:
> >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:           www/mod_rivet
> >broken because:   
> >build errors:       none.
> >overview:         
> >http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=mod_rive
> >t
> >
> >
> >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 at FreeBSD.org>, so that he can attempt to fix the
> >problem in the future.
> >
> >Thanks for your efforts to help improve FreeBSD.

Pietro Cerutti
gahr at gahr.ch

PGP Public Key:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 949 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-apache/attachments/20141029/182789e0/attachment.sig>

More information about the freebsd-apache mailing list