From: Martin Hollingsworth <Martin.Hollingsworth@itk-engineering.de>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] how to configure perl scripting to compile with thread support?
Date: Thu, 24 Apr 2014 11:28:02 +0000 [thread overview]
Message-ID: <1CFDA15477ACF741AAF78FA447550B7A028E072B@swexchange01.itk.local> (raw)
In-Reply-To: <20140424074953.GQ3804@pengutronix.de>
> Just speculating here: Did you try to set -Duseithreads instread of -Dusethreads?
> At least in 5.18.2 these seem to be separate options. I have no idea what the difference is.
Yes, I tried both separately which had no effect.
When using both flags together perl seems to be built with threading enabled (perl -V gives: "useithreads=define"), but starting any of the previous mentioned test code snippets result in a Segmentation Fault as soon as any thread related feature is used.
My current make file looks like this, the only modifications from stock ptxdist are the -Duse(i)thread lines.
--------------
PERL_CONF_OPT := \
-Dusethreads -A ldflags=-pthread\
-Duseithreads -A ldflags=-pthread\
--prefix=/usr \
$(CROSS_AUTOCONF_ARCH) \
--target=$(PTXCONF_GNU_TARGET) \
--set-ld=$(CROSS_CC)
--------------
Regards,
Martin
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-04-24 11:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 8:49 Martin Hollingsworth
2014-04-22 11:00 ` Bernhard Walle
2014-04-22 12:09 ` Martin Hollingsworth
2014-04-22 12:20 ` Bernhard Walle
2014-04-22 12:45 ` Martin Hollingsworth
2014-04-22 13:07 ` Bernhard Walle
2014-04-22 13:50 ` Martin Hollingsworth
2014-04-22 20:55 ` Bernhard Walle
2014-04-23 11:50 ` Martin Hollingsworth
2014-04-23 14:44 ` Martin Hollingsworth
2014-04-24 7:49 ` Michael Olbrich
2014-04-24 11:28 ` Martin Hollingsworth [this message]
2014-04-22 14:48 ` 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=1CFDA15477ACF741AAF78FA447550B7A028E072B@swexchange01.itk.local \
--to=martin.hollingsworth@itk-engineering.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