1 From 0f7bf4706d2932aaa50904fc529a853c9f86478f Mon Sep 17 00:00:00 2001
2 From: Waldemar Brodkorb <wbx@openadk.org>
3 Date: Mon, 13 Feb 2017 22:18:11 +0100
4 Subject: [PATCH] uClibc-ng is compatible to glibc
6 Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
8 Pull-Request: https://github.com/xelerance/Openswan/pull/227
11 linux/include/openswan.h | 12 ------------
12 1 file changed, 12 deletions(-)
14 diff --git a/linux/include/openswan.h b/linux/include/openswan.h
15 index e2c45a130..66b9d42b2 100644
16 --- a/linux/include/openswan.h
17 +++ b/linux/include/openswan.h
22 - * When using uclibc, malloc(0) returns NULL instead of success. This is
23 - * to make it use the inbuilt work-around.
24 - * See: http://osdir.com/ml/network.freeswan.devel/2003-11/msg00009.html
27 -# if !defined(__MALLOC_GLIBC_COMPAT__) && !defined(MALLOC_GLIBC_COMPAT)
28 -# warning Please compile uclibc with GLIBC_COMPATIBILITY defined
34 * We've just got to have some datatypes defined... And annoyingly, just
35 * where we get them depends on whether we're in userland or not.