On 01/08/2015 10:13 PM, [email protected] wrote:
> Author: igor
> Date: Thu Jan  8 13:13:29 2015
> New Revision: 3108
> 
> Log:
> fix qt4 build with libressl
> 
> Added:
>    
> trunk/qt-everywhere-opensource-src/qt-everywhere-opensource-src-4.8.6-libressl-1.patch
> 
> Added: 
> trunk/qt-everywhere-opensource-src/qt-everywhere-opensource-src-4.8.6-libressl-1.patch
> ==============================================================================
> --- /dev/null 00:00:00 1970   (empty, because file is newly added)
> +++ 
> trunk/qt-everywhere-opensource-src/qt-everywhere-opensource-src-4.8.6-libressl-1.patch
>     Thu Jan  8 13:13:29 2015        (r3108)
> @@ -0,0 +1,18 @@
> +Submitted By:            Igor Živković <[email protected]>
> +Date:                    2015-01-08
> +Initial Package Version: 4.8.6
> +Upstream Status:         Not submitted
> +Origin:                  Self
> +Description:             Fixes build with LibreSSL.
> +
> +diff -Naur 
> qt-everywhere-opensource-src-4.8.6.orig/src/network/ssl/qsslsocket_openssl_p.h
>  qt-everywhere-opensource-src-4.8.6/src/network/ssl/qsslsocket_openssl_p.h
> +--- 
> qt-everywhere-opensource-src-4.8.6.orig/src/network/ssl/qsslsocket_openssl_p.h
>    2014-04-10 20:37:12.000000000 +0200
> ++++ 
> qt-everywhere-opensource-src-4.8.6/src/network/ssl/qsslsocket_openssl_p.h     
>    2015-01-08 22:09:55.690756918 +0100
> +@@ -72,6 +72,7 @@
> + #include <openssl/pkcs12.h>
> + #include <openssl/pkcs7.h>
> + #include <openssl/rand.h>
> ++#include <stdint.h>
> + #include <openssl/ssl.h>
> + #include <openssl/stack.h>
> + #include <openssl/x509.h>
> 

Just curious.

I saw that several patches for libressl only add #include <stdint.h>
before #include <openssl/ssl.h>. Any specific reason why you did not
turn such patches into simple sed's?

-- 
Note: My last name is not Krejzi.

Attachment: signature.asc
Description: OpenPGP digital signature

-- 
http://lists.linuxfromscratch.org/listinfo/patches
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to