complibs/ppl: build only C and C++ interfaces for PPL
By default, PPL wants to build interfaces for any of a variety of
langauges it finds on the local host (python, java, possibly perl, also
more esoteric languages such as ocaml and prolog).
These extra interfaces can double the compile time for the library. For
single-process builds, I found a savings of more than 40%:
default / j1: 716s total, 143.2s avg, 0.52s stdev
just_c / j1: 406s total, 81.2s avg, 0.33s stdev
just_c_cpp / j1: 413s total, 82.6s avg, 0.22s stdev
And for multi-process builds, it approached 50%:
default / j4: 625s total, 125.0s avg, 0.57s stdev
just_c / j4: 338s total, 67.6s avg, 1.25s stdev
just_c_cpp / j4: 327s total, 65.4s avg, 0.36s stdev
Since the PPL we build within ct-ng is only used by GCC, we only need to
build the C and C++ interfaces.
Signed-Off-By: Anthony Foiani <anthony.foiani@gmail.com>
1 Original patch from: gentoo/src/patchsets/glibc/2.9/5070_all_glibc-2.7-cross-compile-nptl.patch
3 -= BEGIN original header =-
4 A little hack for cross-compiling NPTL
6 http://sourceware.org/ml/libc-alpha/2005-02/msg00043.html
8 -= END original header =-
10 diff -durN glibc-2_9.orig/nptl/sysdeps/pthread/configure glibc-2_9/nptl/sysdeps/pthread/configure
11 --- glibc-2_9.orig/nptl/sysdeps/pthread/configure 2007-10-17 00:24:30.000000000 +0200
12 +++ glibc-2_9/nptl/sysdeps/pthread/configure 2009-02-02 22:01:28.000000000 +0100
15 { echo "$as_me:$LINENO: result: $libc_cv_forced_unwind" >&5
16 echo "${ECHO_T}$libc_cv_forced_unwind" >&6; }
17 +if test $libc_cv_forced_unwind = no -a $build_cpu != $host_cpu; then
18 + echo "$as_me:$LINENO: forcing libc_cv_forced_unwind = yes for cross-compile"
19 + libc_cv_forced_unwind=yes
21 if test $libc_cv_forced_unwind = yes; then
22 cat >>confdefs.h <<\_ACEOF
23 #define HAVE_FORCED_UNWIND 1
25 { echo "$as_me:$LINENO: result: $libc_cv_c_cleanup" >&5
26 echo "${ECHO_T}$libc_cv_c_cleanup" >&6; }
28 + if test $libc_cv_c_cleanup = no -a $build_cpu != $host_cpu; then
29 + echo "$as_me:$LINENO: result: forcing libc_cv_c_cleanup = yes for cross-compile"
30 + libc_cv_c_cleanup=yes
32 if test $libc_cv_c_cleanup = no; then
33 { { echo "$as_me:$LINENO: error: the compiler must support C cleanup handling" >&5
34 echo "$as_me: error: the compiler must support C cleanup handling" >&2;}
35 diff -durN glibc-2_9.orig/nptl/sysdeps/pthread/configure.in glibc-2_9/nptl/sysdeps/pthread/configure.in
36 --- glibc-2_9.orig/nptl/sysdeps/pthread/configure.in 2003-12-03 07:50:01.000000000 +0100
37 +++ glibc-2_9/nptl/sysdeps/pthread/configure.in 2009-02-02 22:01:28.000000000 +0100
39 struct _Unwind_Context *context;
40 _Unwind_GetCFA (context)],
41 libc_cv_forced_unwind=yes, libc_cv_forced_unwind=no)])
42 +if test $libc_cv_forced_unwind = no -a $build_cpu != $host_cpu; then
43 + libc_cv_forced_unwind=yes
45 if test $libc_cv_forced_unwind = yes; then
46 AC_DEFINE(HAVE_FORCED_UNWIND)
47 dnl Check for C cleanup handling.
50 libc_cv_c_cleanup=yes, libc_cv_c_cleanup=no)])
52 + if test $libc_cv_c_cleanup = no -a $build_cpu != $host_cpu; then
53 + libc_cv_c_cleanup=yes
55 if test $libc_cv_c_cleanup = no; then
56 AC_MSG_ERROR([the compiler must support C cleanup handling])