summaryrefslogtreecommitdiff
path: root/archivers/liblzo/patches
diff options
context:
space:
mode:
authorreinoud <reinoud>2004-04-09 21:40:14 +0000
committerreinoud <reinoud>2004-04-09 21:40:14 +0000
commit1dd67466e45b6f653b8f9aa39de458f5b13d72df (patch)
tree445cd902566c45db4192d917f5c7beaab1983942 /archivers/liblzo/patches
parent9af0ab930e4cf9d0056b02ec460ff714a85febc0 (diff)
downloadpkgsrc-1dd67466e45b6f653b8f9aa39de458f5b13d72df.tar.gz
Comment out a most likely allready redundant compilation time check that
made it bomb out during compilation. Propably Linux paranoia/ignorance? The problem occured on NetBSD/shark 1.5ZG and with the patch compiles without any warnings.
Diffstat (limited to 'archivers/liblzo/patches')
-rw-r--r--archivers/liblzo/patches/patch-aa14
1 files changed, 14 insertions, 0 deletions
diff --git a/archivers/liblzo/patches/patch-aa b/archivers/liblzo/patches/patch-aa
new file mode 100644
index 00000000000..24bb0166edd
--- /dev/null
+++ b/archivers/liblzo/patches/patch-aa
@@ -0,0 +1,14 @@
+$NetBSD: patch-aa,v 1.5 2004/04/09 21:40:14 reinoud Exp $
+
+--- src/lzo_init.c.orig 2002-07-13 01:31:52.000000000 +0000
++++ src/lzo_init.c
+@@ -169,7 +169,8 @@ static lzo_bool basic_integral_check(voi
+ COMPILE_TIME_ASSERT(LZO_UINT32_MAX == LZO_UTYPE_MAX(sizeof(lzo_uint32)));
+ COMPILE_TIME_ASSERT(LZO_UINT_MAX == LZO_UTYPE_MAX(sizeof(lzo_uint)));
+ #if !defined(__LZO_IN_MINILZO)
+- COMPILE_TIME_ASSERT(SIZE_T_MAX == LZO_UTYPE_MAX(sizeof(size_t)));
++/* is this redundant ? */
++/* COMPILE_TIME_ASSERT(SIZE_T_MAX == LZO_UTYPE_MAX(sizeof(size_t))); */
+ #endif
+
+ r &= __lzo_assert(LZO_BYTE(257) == 1);