mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] how to configure perl scripting to compile with thread support?
Date: Thu, 24 Apr 2014 09:49:53 +0200	[thread overview]
Message-ID: <20140424074953.GQ3804@pengutronix.de> (raw)
In-Reply-To: <1CFDA15477ACF741AAF78FA447550B7A028DF618@swexchange01.itk.local>

On Wed, Apr 23, 2014 at 02:44:14PM +0000, Martin Hollingsworth wrote:
> Here some more info I found in the meantime.
> You can call "perl -V" which gives a lot of information about the build settings.
> The target system outputs:
> ---------
> [...]
>   Platform:
>     osname=linux, osvers=current, archname=arm-linux
>     uname='arm-cortexa8-linux-gnueabihf'
>     config_args='-Dusethreads -A ldflags=-pthread --prefix=/usr --host=arm-cortexa8-linux-gnueabihf --build=i686-host-linux-gnu --host=arm-cortexa8-linux-gnueabihf --target=arm-cortexa8-linux-gnueabihf --set-ld=arm-cortexa8-linux-gnueabihf-gcc --keeplog --mode=target --target=arm-cortexa8-linux-gnueabihf --targetarch=arm-cortexa8-linux-gnueabihf'
> [...]
>     useithreads=undef, usemultiplicity=undef
> [...]
> ---------
> 
> As one can see from config_args the flag -Dusethreads is received, but the Perl internal flag "useithreads" stays undef. On my host this value is "defined" and threading works.
> When you look into the config.sh file  (Shortened path: /BSP/phyCORE-AM335x-XXX/platform-XXX/build-target/perl-5.14.2/config.sh) which is generated by perl itself during the ptxdist build process, you will find this particular flag undef here as well.
> I suppose this is the root of all evil - the perl config.sh file is not generated correctly. The question now is why...?

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.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-04-24  7:49 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 [this message]
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=20140424074953.GQ3804@pengutronix.de \
    --to=m.olbrich@pengutronix.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