ad8a707fdf
libfaad uses data types with machine dependent bit width in prototypes in its public headers, but in the corresponding library code, machine independent exact width data types are used. solution: change libfaad headers to use the same machine independent exact width data types in the prototypes as in the library. since the prototypes in the library headers are changed, users of libfaad likely need to be modified to use exact width data types as well. also: - bump libfaad major version number - update plugin code to use exact width data types for libfaad interaction, as per new prototypes - bump package version - sync patches with update-patches problem discovered by, solution discussed with, reviewed, tested and OK naddy@
16 lines
521 B
Plaintext
16 lines
521 B
Plaintext
$OpenBSD: patch-configure_in,v 1.4 2007/06/29 06:01:42 jakemsr Exp $
|
|
--- configure.in.orig Fri Feb 6 08:04:39 2004
|
|
+++ configure.in Thu May 31 14:07:32 2007
|
|
@@ -67,10 +67,7 @@ MY_CHECK_TYPEDEF_FROM_INCLUDE([fpos_t foo; foo.__pos =
|
|
[HAVE_FPOS_T_POS])
|
|
|
|
|
|
-external_mp4v2=yes
|
|
-AC_CHECK_LIB(mp4v2, MP4Create, , external_mp4v2=no, -lstdc++)
|
|
-AC_CHECK_LIB(mp4v2, MP4MetadataDelete, , external_mp4v2=no, -lstdc++)
|
|
-AC_CHECK_HEADER(mp4.h, , external_mp4v2=no)
|
|
+external_mp4v2=no
|
|
|
|
AM_CONDITIONAL(WITH_MP4V2, false)
|
|
|