aalib-x11 and aview-x11.
SDL dependencies change, so bump PKGREVISION (and BUILDLINK_RECOMMENDED)
for affected packages.
Addresses PR 32046 by Leonard Schmidt.
error: label at end of compound statement
error: array bound forbidden after parenthesized type-id
This was noticed on FreeBSD 5.4-STABLE with gcc 3.4.2.
Also test build under NetBSD 1.6.2_STABLE with gcc 2.95.3
and Linux with gcc 3.3.5.
No PKGREVISION bump since this should not change anything.
This package does not have a maintainer.
And remove from PLIST.
This fixes problem when INFO_DIR is using a custom directory such
as share/info.
Do not bump PKGREVISION, because couldn't package in first place when
this problem occurred.
This will cause a warning:
install-info: warning: no info dir entry in `/usr/pkg/share/info/mjpeg-howto.info'
TODO: so add a START-INFO-DIR-ENTRY/END-INFO-DIR-ENTRY pair dir entry.
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
by moving the inclusion of buildlink3.mk files outside of the protected
region. This bug would be seen by users that have set PREFER_PKGSRC
or PREFER_NATIVE to non-default values.
BUILDLINK_PACKAGES should be ordered so that for any package in the
list, that package doesn't depend on any packages to the left of it
in the list. This ordering property is used to check for builtin
packages in the correct order. The problem was that including a
buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed
from BUILDLINK_PACKAGES and appended to the end. However, since the
inclusion of any other buildlink3.mk files within that buildlink3.mk
was in a region that was protected against multiple inclusion, those
dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
Changes:
Since the authors don't provide a proper CHANGES file/release announcement, this
is me guess from diffing to last version (1.6.1.93):
- aix build fixes
- icc support
- doc updates
- yuvfps tries to find a normalized framerate by default
... and probably the usual: bug-fixes
