complibs/ppl: update GMP location configuration argument for PPL v0.11 and later
'configure' for PPL 0.11 (and later) needs "--with-gmp-prefix" to
provide the location of the GMP toolkit; the previous switches were
"--with-libgmp-prefix" and "--with-libgmpxx-prefix".
The upstream log message is:
commit 08dfb6fea094f8c5a533575a3ea2095edce99a6d
Author: Roberto Bagnara <bagnara@cs.unipr.it>
Date: Sun Jul 12 21:39:46 2009 +0200
New configure option --with-gmp-prefix supersedes the (now removed)
options --with-libgmp-prefix and --with-libgmpxx-prefix.
Link: http://www.cs.unipr.it/git/gitweb.cgi?p=ppl/ppl.git;a=commit;h=08dfb6fea094f8c5a533575a3ea2095edce99a6d
Since PPL's 'configure' ignores unknown switches, we use all three so we
don't have to conditionalize the ppl.sh build script itself.
Signed-Off-By: Anthony Foiani <anthony.foiani@gmail.com>
(transplanted from 4f0c4fb572e2862c24b28e8d27ce7e9cb9adba65)
2 Helper Makefile for testing gcc toolchains using the gcc-testsuite
3 ==================================================================
8 * DejaGnu 'runtest' v1.4.4+
15 Edit default.cfg to reflect your toolchain and target configuration.
17 Alternatively, override configuration variables on the command line.
19 Available config variables:
22 The name of the tool you want to test.
23 Currently supported: gcc or g++
27 The hostname or IP of the machine to execute run-tests
31 Execute the run-test as this user on DG_TARGET_HOSTNAME
36 The C/C++ tests you want to check
37 Default: (empty, means all tests)
43 The first two examples require a networked target with ssh access and automatic
44 ssh login (see section below). Target SW should be compiled with the toolchain
47 Run default gcc compile/execution tests:
48 $ make DG_TOOLNAME=gcc DG_TARGET_HOSTNAME=192.168.17.93 DG_TARGET_USERNAME=root
50 Run default g++ compile/execution tests:
51 $ make DG_TOOLNAME=g++ DG_TARGET_HOSTNAME=192.168.17.93 DG_TARGET_USERNAME=root
53 Run selected gcc compile only tests (no target required):
54 $ make DG_TOOLNAME=gcc DG_C_TESTS="compile.exp noncompile.exp"
57 SSH automatic login configuration example
58 -----------------------------------------
61 ssh-keygen -t rsa (then simply press enter thru all steps)
62 ssh-copy-id -i ~/.ssh/id_rsa.pub <username>@<target IP>
64 Now automatic ssh login should work - test by doing a simple ssh session to target.
66 Note: The procedure might be slightly different for your particular target.
69 Getting rid of the test-suite
70 -----------------------------
72 If you no longer have a need for the test-suite, then you can remove it altogether
73 from your toolchain. Just delete the test-suite/ dub-dir.
78 Martin Lund <mgl@doredevelopment.dk>
81 "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
82 Getting rid of the test-suite