From: "André Draszik" <git@andred.net>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: small number of perl modules that can't be cross-compiled
Date: Fri, 18 Nov 2016 12:27:48 +0000 [thread overview]
Message-ID: <1479472068.27546.12.camel@andred.net> (raw)
In-Reply-To: <alpine.LFD.2.20.1611180634400.3556@localhost.localdomain>
On Fri, 2016-11-18 at 06:41 -0500, Robert P. J. Day wrote:
> after OE recipfying over 100 perl modules from CPAN, i'm down to
> less than a dozen that are going to take more work, and a small number
> of those seem to be simply badly written in that they don't support
> cross-compilation for my target choice of "qemuppc". example
> boilerplate recipe i put together produces this:
>
> $ make libauthen-pam-perl
> ... snip ...
> Checking if your kit is complete...
> Looks good
> checking for gcc... powerpc-wrs-linux-gcc -m32 -mhard-float -mcpu=7400
> --
> sysroot=/home/rpjday/WRL/builds/msm/nov17/bitbake_build/tmp/sysroots/qemup
> pc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... configure: error: cannot run
> C compiled programs.
> If you meant to cross compile, use `--host'.
> See `config.log' for more details.
It'd be useful to see config.log, ...
> Error in configuring the Authen::PAM module.
> ... snip ...
>
> so i'm assuming the source itself for Authen::PAM:
>
> https://metacpan.org/pod/Authen::PAM
>
> is somehow flawed in that it doesn't properly recognize
> cross-compilation, would that be it?
... there is at least one issue in Authen-PAM-0.16/configure.ac, I would
say, in that it tries to detect RTLD_GLOBAL support based on the host's
perl. So it's likely there are more flaws.
A.
next prev parent reply other threads:[~2016-11-18 12:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 11:41 small number of perl modules that can't be cross-compiled Robert P. J. Day
2016-11-18 12:27 ` André Draszik [this message]
2016-11-18 12:46 ` Robert P. J. Day
2016-11-18 13:15 ` André Draszik
2016-11-18 14:09 ` Robert P. J. Day
2016-11-18 14:50 ` André Draszik
2016-11-18 14:55 ` Robert P. J. Day
2016-11-18 13:03 ` Jens Rehsack
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=1479472068.27546.12.camel@andred.net \
--to=git@andred.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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