From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "André Draszik" <git@andred.net>
Cc: 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 07:46:28 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.20.1611180742360.16475@localhost.localdomain> (raw)
In-Reply-To: <1479472068.27546.12.camel@andred.net>
[-- Attachment #1: Type: text/plain, Size: 4670 bytes --]
On Fri, 18 Nov 2016, André Draszik wrote:
> 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, ...
see bottom.
> > 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.
that's pretty much all i wanted to confirm at this point -- that it
wasn't something stupid i was doing; rather, the source itself is
flawed, and that's not the only example.
rday
DEBUG: Executing python function sysroot_cleansstate
DEBUG: Python function sysroot_cleansstate finished
DEBUG: Executing shell function do_configure
*** Module name IN: /home/rpjday/WRL/builds/msm/nov17/bitbake_build/tmp/sysroots/qemuppc/usr/lib/perl/5.22.0/Cwd.pm
*** p1: /home/rpjday/WRL/builds/msm/nov17/bitbake_build/tmp/sysroots/qemuppc/usr/lib/ p3: perl/5.22.0/ p5: Cwd.pm
*** Module name OUT: /home/rpjday/WRL/builds/msm/nov17/bitbake_build/tmp/sysroots/x86_64-linux/usr/lib/perl-native/perl/5.22.0/Cwd.pm
*** Module name IN: /home/rpjday/WRL/builds/msm/nov17/bitbake_build/tmp/sysroots/qemuppc/usr/lib/perl/5.22.0/Encode.pm
*** p1: /home/rpjday/WRL/builds/msm/nov17/bitbake_build/tmp/sysroots/qemuppc/usr/lib/ p3: perl/5.22.0/ p5: Encode.pm
*** Module name OUT: /home/rpjday/WRL/builds/msm/nov17/bitbake_build/tmp/sysroots/x86_64-linux/usr/lib/perl-native/perl/5.22.0/Encode.pm
*** Module name IN: /home/rpjday/WRL/builds/msm/nov17/bitbake_build/tmp/sysroots/qemuppc/usr/lib/perl/5.22.0/I18N/Langinfo.pm
*** p1: /home/rpjday/WRL/builds/msm/nov17/bitbake_build/tmp/sysroots/qemuppc/usr/lib/ p3: perl/5.22.0/ p5: I18N/Langinfo.pm
*** Module name OUT: /home/rpjday/WRL/builds/msm/nov17/bitbake_build/tmp/sysroots/x86_64-linux/usr/lib/perl-native/perl/5.22.0/I18N/Langinfo.pm
*** Module name IN: /home/rpjday/WRL/builds/msm/nov17/bitbake_build/tmp/sysroots/qemuppc/usr/lib/perl/5.22.0/B.pm
*** p1: /home/rpjday/WRL/builds/msm/nov17/bitbake_build/tmp/sysroots/qemuppc/usr/lib/ p3: perl/5.22.0/ p5: B.pm
*** Module name OUT: /home/rpjday/WRL/builds/msm/nov17/bitbake_build/tmp/sysroots/x86_64-linux/usr/lib/perl-native/perl/5.22.0/B.pm
*** Module name IN: /home/rpjday/WRL/builds/msm/nov17/bitbake_build/tmp/sysroots/qemuppc/usr/lib/perl/5.22.0/List/Util.pm
*** p1: /home/rpjday/WRL/builds/msm/nov17/bitbake_build/tmp/sysroots/qemuppc/usr/lib/ p3: perl/5.22.0/ p5: List/Util.pm
*** Module name OUT: /home/rpjday/WRL/builds/msm/nov17/bitbake_build/tmp/sysroots/x86_64-linux/usr/lib/perl-native/perl/5.22.0/List/Util.pm
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/qemuppc
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.
Error in configuring the Authen::PAM module.
WARNING: /home/rpjday/WRL/builds/msm/nov17/bitbake_build/tmp/work/ppc7400-wrs-linux/libauthen-pam-perl/0.16-r0/temp/do_configure/run.do_configure.16119:1 exit 25 from
perl Makefile.PL INSTALLDIRS=vendor
ERROR: Function failed: do_configure (log file is located at /home/rpjday/WRL/builds/msm/nov17/bitbake_build/tmp/work/ppc7400-wrs-linux/libauthen-pam-perl/0.16-r0/temp/do_configure/log.do_configure.16119)
next prev parent reply other threads:[~2016-11-18 12:47 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
2016-11-18 12:46 ` Robert P. J. Day [this message]
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=alpine.LFD.2.20.1611180742360.16475@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=git@andred.net \
--cc=openembedded-core@lists.openembedded.org \
/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