complibs/ppl: fix 0.11-0.11.2 to compile with --disable-shared
PPL 0.11 (through 0.11.2) had a small bug where it still tried to build
and test its Java interface even when shared libraries are disabled.
Since that's exactly what ct-ng does, it explodes.
This is the patch from the PPL authors (see final link below).
More information can be found in these messages/threads:
Anthony's initial report and analysis with Yann:
http://www.cygwin.com/ml/crossgcc/2011-05/msg00046.html
Ron Flory hit the same problem:
http://www.cygwin.com/ml/crossgcc/2011-05/msg00054.html
Anthony's report to the ppl-devel list:
http://www.cs.unipr.it/pipermail/ppl-devel/2011-May/017450.html
Roberto's reply with a link to the fix in the PPL git repo:
http://www.cs.unipr.it/pipermail/ppl-devel/2011-May/017455.html
Signed-Off-By: Anthony Foiani <anthony.foiani@gmail.com>
(transplanted from 139b85d70b623e51f7585e7c64ecb8c6a6cf4567)
1 From: Tomoyoshi ASANO <asa@lineo.co.jp>
2 Message ID: <20081208073522.0AEF.22C34B8C@lineo.co.jp>
6 I have SEGV at busybox's telnet with uClibc-0.9.30.
7 It seem the current uClibc-trunk has the same problem.
12 diff -ru uClibc-0.9.30.orig/libc/inet/getaddrinfo.c uClibc-0.9.30/libc/inet/getaddrinfo.c
13 --- uClibc-0.9.30.orig/libc/inet/getaddrinfo.c 2008-10-28 17:25:10.000000000 +0100
14 +++ uClibc-0.9.30/libc/inet/getaddrinfo.c 2009-02-26 14:20:06.000000000 +0100
19 - for (runp = ifa; runp != NULL; runp = runp->ifa_next)
20 + for (runp = ifa; runp != NULL; runp = runp->ifa_next) {
21 #if defined __UCLIBC_HAS_IPV4__
22 if (runp->ifa_addr->sa_family == PF_INET)
25 if (runp->ifa_addr->sa_family == PF_INET6)
27 #endif /* __UCLIBC_HAS_IPV6__ */