Author: igor
Date: Mon Aug 19 01:46:37 2013
New Revision: 2713

Log:
boost patch filename format

Added:
   trunk/boost/boost-1.54.0-glibc-1.patch
      - copied unchanged from r2712, trunk/boost/boost_1_54_0-glibc-1.patch
Deleted:
   trunk/boost/boost_1_54_0-glibc-1.patch

Copied: trunk/boost/boost-1.54.0-glibc-1.patch (from r2712, 
trunk/boost/boost_1_54_0-glibc-1.patch)
==============================================================================
--- /dev/null   00:00:00 1970   (empty, because file is newly added)
+++ trunk/boost/boost-1.54.0-glibc-1.patch      Mon Aug 19 01:46:37 2013        
(r2713, copy of r2712, trunk/boost/boost_1_54_0-glibc-1.patch)
@@ -0,0 +1,22 @@
+Submitted By:            Igor Živković <[email protected]>
+Date:                    2013-08-18
+Initial Package Version: 1_54_0
+Upstream Status:         Fixed
+Origin:                  Upstream
+Description:             Fixes compiling with Glibc-2.18.
+
+diff -Naur boost_1_54_0.orig/boost/cstdint.hpp boost_1_54_0/boost/cstdint.hpp
+--- boost_1_54_0.orig/boost/cstdint.hpp        2013-03-09 23:55:05.000000000 
+0100
++++ boost_1_54_0/boost/cstdint.hpp     2013-08-18 21:45:19.223003705 +0200
+@@ -41,7 +41,10 @@
+ // so we disable use of stdint.h when GLIBC does not define 
__GLIBC_HAVE_LONG_LONG.
+ // See https://svn.boost.org/trac/boost/ticket/3548 and 
http://sources.redhat.com/bugzilla/show_bug.cgi?id=10990
+ //
+-#if defined(BOOST_HAS_STDINT_H) && (!defined(__GLIBC__) || 
defined(__GLIBC_HAVE_LONG_LONG))
++#if defined(BOOST_HAS_STDINT_H)                                 \
++  && (!defined(__GLIBC__)                                       \
++      || defined(__GLIBC_HAVE_LONG_LONG)                        \
++      || (defined(__GLIBC__) && ((__GLIBC__ > 2) || ((__GLIBC__ == 2) && 
(__GLIBC_MINOR__ >= 17)))))
+ 
+ // The following #include is an implementation artifact; not part of 
interface.
+ # ifdef __hpux
-- 
http://linuxfromscratch.org/mailman/listinfo/patches
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to