From owner-freebsd-ports@FreeBSD.ORG  Wed Mar 12 08:32:52 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 06035EAA
 for <freebsd-ports@freebsd.org>; Wed, 12 Mar 2014 08:32:52 +0000 (UTC)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 92D27B2B
 for <freebsd-ports@freebsd.org>; Wed, 12 Mar 2014 08:32:51 +0000 (UTC)
Received: from mandree.no-ip.org ([78.49.41.220]) by mail.gmx.com (mrgmx101)
 with ESMTPSA (Nemesis) id 0LtVLE-1X6zlo0Xgq-010xog for
 <freebsd-ports@freebsd.org>; Wed, 12 Mar 2014 09:32:44 +0100
Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1])
 by apollo.emma.line.org (Postfix) with ESMTP id 8075223DA2F
 for <freebsd-ports@freebsd.org>; Wed, 12 Mar 2014 09:32:41 +0100 (CET)
Message-ID: <53201BA9.2020105@gmx.de>
Date: Wed, 12 Mar 2014 09:32:41 +0100
From: Matthias Andree <matthias.andree@gmx.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: freebsd-ports@freebsd.org
Subject: Re: What's up with pkg-fallout?
References: <531FBD31.9060300@missouri.edu>
In-Reply-To: <531FBD31.9060300@missouri.edu>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:7f8hjeUGtF08AChrU+CdiUtYwq0vMW3BytNc99t2lNzjZGI0mPY
 sVurdhzRAv7LVvRQDA0gLZ8M23HqWIrS6sdQd//Uc6cOHXR6Jhp0cyV4ZDYVue5bpiiExdD
 yYi7pTSgFfUpKsLVdOuFGfdCEjZqba5M1GzOlWDH6a0YHmKDRt/gyfRpibU9K3OBEsWKv1v
 Fz5Kw3ytodqFwhkbmpshA==
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Mar 2014 08:32:52 -0000

Am 12.03.2014 02:49, schrieb Montgomery-Smith, Stephen:
> I keep getting emails from pkg-fallout@ that some of my ports are
> faulty.  But it is obvious that pkg-fallout sometimes uses a really old
> ports trees.  And the errors it is reporting have been fixed weeks ago.

Also, if one looks at
<http://beefy1.isc.freebsd.org/bulk/10i386-default/2014-03-06_05h10m01s/logs/rawtherapee-4.0.12_1.log>
it looks rather implausible to me.  Meaning that: 10i386 complains about
undeclared free() and malloc(), but 10amd64 does not complain, and
looking at the sources, I find the compiler errors implausible.
  I also cannot reproduce the problem on 10.0-RELEASE at home, so I
believe that the fallout 10i386 builder is broken in some way at least
for C++ ports.

Please someone investigate.