mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Bernhard Walle <bernhard@bwalle.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] how to configure perl scripting to compile with thread support?
Date: Tue, 22 Apr 2014 22:55:25 +0200	[thread overview]
Message-ID: <20140422205525.GA89375@euler.fritz.box> (raw)
In-Reply-To: <1CFDA15477ACF741AAF78FA447550B7A028DF487@swexchange01.itk.local>

Hello Martin,

* Martin Hollingsworth <Martin.Hollingsworth@itk-engineering.de> [2014-04-22 15:50]:
> a simple one liner could be like this. Including the threads module already causes the error.
> ---------test.pl----------
> #!/usr/bin/perl
> use threads;
> print "\n Hello World";
> ---------------------------
> In the meantime a complete rebuild of the target after "ptxdist distclean" has finished, but the error still appears.

my patch to enable Perl is now against git master of ptxdist (which has
an updated version of Perl).

I tested in on a target (Raspberry Pi) and it works:

Disabled threads:

    root@vetero:~ perl -mthreads -e 'print "x\n";'
    This Perl not built to support threads
    Compilation failed in require.
    BEGIN failed--compilation aborted.

Enabled threads:

    root@vetero:~ perl -mthreads -e 'print "x\n";'
    x

Regards,
Bernhard

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-04-22 20:55 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 [this message]
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
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=20140422205525.GA89375@euler.fritz.box \
    --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