Openembedded Core Discussions
 help / color / mirror / Atom feed
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 09:55:22 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.20.1611180954500.19358@localhost.localdomain> (raw)
In-Reply-To: <1479480655.27546.16.camel@andred.net>

[-- Attachment #1: Type: text/plain, Size: 2854 bytes --]

On Fri, 18 Nov 2016, André Draszik wrote:

> On Fri, 2016-11-18 at 09:09 -0500, Robert P. J. Day wrote:
> > On Fri, 18 Nov 2016, André Draszik wrote:
> >
> > > On Fri, 2016-11-18 at 07:46 -0500, Robert P. J. Day wrote:
> > > > 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/sysroo
> > > > > > ts/q
> > > > > > emup
> > > > > > 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.
> > >
> > > That message is referring to config.log from autotools, not the
> > > bitbake do_configure.log. Should be somewhere below ${B}
> >
> >   sorry, my mistake ... see below:
> >
> > This file contains any messages produced by compilers while
> > running configure, to aid debugging if configure makes a mistake.
> >
> > It was created by Authen::PAM configure 0.16, which was
> > generated by GNU Autoconf 2.59.  Invocation command line was
> >
> >   $ ./configure
>
> I think the issues are in your recipe. You should see *many* arguments to
> configure. In particular --build= --host= --target=, but many more.
>
> Also, this explains that message:
>
> configure:1697: error: cannot run C compiled programs.
> If you meant to cross compile, use `--host'.

  i realize that now, so that will be today's project. thanks.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

  reply	other threads:[~2016-11-18 14:56 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
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 [this message]
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.1611180954500.19358@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