Date: Sun, 4 Apr 2010 18:58:40 -0700 From: Garrett Cooper <yanefbsd@gmail.com> To: FreeBSD Ports <ports@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>, Xin Li <delphij@freebsd.org> Subject: Re: Ports breakage since r205471 Message-ID: <n2h7d6fde3d1004041858v5b19feedm7260849d065847f6@mail.gmail.com> In-Reply-To: <l2g7d6fde3d1004041506i1a32806bl1905d2ed4eb9e599@mail.gmail.com> References: <l2g7d6fde3d1004041506i1a32806bl1905d2ed4eb9e599@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 4, 2010 at 3:06 PM, Garrett Cooper <yanefbsd@gmail.com> wrote:
> Hi all,
> =A0 =A0I 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.
> =A0 =A0The following 3rd party libraries and all of their dependencies:
>
> graphics/png
> graphics/tiff
> textproc/libxml2
>
> =A0 all needed to be rebuilt.
> =A0 The following items incorrectly define LARGEFILE64 and result in
> errors like the following:
>
> /usr/include/zlib.h:1561: error: expected '=3D', ',', ';', 'asm' or
> '__attribute__' before 'gzseek64'
> /usr/include/zlib.h:1562: error: expected '=3D', ',', ';', 'asm' or
> '__attribute__' before 'gztell64'
> /usr/include/zlib.h:1563: error: expected '=3D', ',', ';', 'asm' or
> '__attribute__' before 'gzoffset64'
> /usr/include/zlib.h:1564: error: expected declaration specifiers or
> '...' before 'off64_t'
> /usr/include/zlib.h:1565: error: expected declaration specifiers or
> '...' before 'off64_t'
>
> devel/qt-moc
> lang/python (uses pieces from gpac-libgpac I think)
> multimedia/gpac-libgpac
> multimedia/vlc (draft patch attached to ports/145387)
>
> =A0 Also, I really think we should add packaging metadata to third
> party libraries in base and at least track the versioning and
> dependencies because this CURRENT upgrade has turned into a royal mess
> and has eaten up more of my time than it should have.
As jsa@ so kindly pointed out, upgrading to r206057 temporarily
alleviates this issue. I'll keep on looking for problematic areas
where this needs to be fixed, but a #warning should probably be added
to the header to catch all of the offenders.
Thanks,
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?n2h7d6fde3d1004041858v5b19feedm7260849d065847f6>