Ports breakage since r205471
yanefbsd at gmail.com
Mon Apr 5 09:30:13 UTC 2010
On Mon, Apr 5, 2010 at 2:12 AM, Erwin Lansing <erwin at freebsd.org> wrote:
> On Mon, Apr 05, 2010 at 02:02:46AM -0700, Xin LI wrote:
>> On 2010/04/05 01:50, Erwin Lansing wrote:
>> > On Sun, Apr 04, 2010 at 03:06:15PM -0700, Garrett Cooper wrote:
>> >> Hi all,
>> >> I realize that this is most suitable for current@ and I'm
>> >> cross-posting, but I wanted to jot down all of the ports broken since
>> >> the zlib version bump so that we can keep track of what's going on and
>> >> what needs to be fixed.
>> > I have just started a new package build against todays HEAD on pointyhat
>> > , actually before seeing this thread, so these, and any others, will be
>> > picked up there. I'll update the list with the results when it finishes
>> > in a day or two.
>> Which svn revision is currently using on the build cluster?
> Unfortunately, we're still using cvs for updating, but I just double
> checked that it is past r206058. The update is less than an hour old
> from cvs.
You won't see the issue unless you roll back to before r206057;
r206057 and r206058 disguise the compatibility issue by completely
zapping the #ifdef _LARGEFILE64_SOURCE and #if _FILE_OFFSET_BITS == 64
More information about the freebsd-ports