From: Bernhard Walle <bernhard@bwalle.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] perl: Make it possible to enable thread support
Date: Tue, 22 Apr 2014 22:53:43 +0200 [thread overview]
Message-ID: <1398200023-10099-1-git-send-email-bernhard@bwalle.de> (raw)
Signed-off-by: Bernhard Walle <bernhard@bwalle.de>
---
rules/perl.in | 12 ++++++++++--
rules/perl.make | 4 +++-
2 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/rules/perl.in b/rules/perl.in
index 6a226de..4823a3e 100644
--- a/rules/perl.in
+++ b/rules/perl.in
@@ -1,17 +1,25 @@
## SECTION=scripting_languages
-config PERL
+menuconfig PERL
tristate
- prompt "perl"
+ prompt "perl "
select LIBC_DL
select LIBC_M
select LIBC_CRYPT
select GCCLIBS_GCC_S
+ select LIBC_PTHREAD if PERL_THREADS
help
Larry Wall's Practical Extraction and Report Language
An interpreted scripting language, known among some as
"Unix's Swiss Army Chainsaw".
+if PERL
+
+config PERL_THREADS
+ bool "Enable threads"
+
+endif
+
menu "perl Extra Modules "
source "generated/perl.in"
endmenu
diff --git a/rules/perl.make b/rules/perl.make
index 86a0ff7..fe09089 100644
--- a/rules/perl.make
+++ b/rules/perl.make
@@ -65,7 +65,9 @@ PERL_CONF_OPT := \
--prefix=/usr \
--host=$(PTXCONF_GNU_TARGET) \
--target=$(PTXCONF_GNU_TARGET) \
- -Dld=$(CROSS_CC)
+ -Dld=$(CROSS_CC) \
+ $(call ptx/ifdef, PTXCONF_PERL_THREADS, -Dusethreads, ) \
+ $(call ptx/ifdef, PTXCONF_PERL_THREADS, -A ldflags=-pthread, )
PERL_MAKE_PAR := NO
--
1.9.1
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2014-04-22 20:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 20:53 Bernhard Walle [this message]
2014-04-23 7:04 ` Michael Olbrich
2014-04-23 7:16 ` Bernhard Walle
2014-04-23 7:16 ` [ptxdist] [PATCH] perl: Enable " Bernhard Walle
2014-04-23 12:45 ` Michael Olbrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1398200023-10099-1-git-send-email-bernhard@bwalle.de \
--to=bernhard@bwalle.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox