From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] Frans Meulenbroeks : flex: added perl to dependencies
Date: Sun, 21 Nov 2010 07:03:20 -0700 [thread overview]
Message-ID: <4CE926A8.3000402@mentor.com> (raw)
In-Reply-To: <E1PKA9U-00040x-SY@melo.openembedded.org>
On 11/21/2010 06:40 AM, git version control wrote:
> Module: openembedded.git
> Branch: org.openembedded.dev
> Commit: c3b5b68541320ed0104d8654a0793251ed0187b9
> URL: http://gitweb.openembedded.net/?p=openembedded.git&a=commit;h=c3b5b68541320ed0104d8654a0793251ed0187b9
>
> Author: Frans Meulenbroeks<fransmeulenbroeks@gmail.com>
> Date: Sun Nov 21 10:15:08 2010 +0100
>
> flex: added perl to dependencies
>
> Without it (rebuilding from packaged staging) I got:
>
> | /home/frans/oe/tmp_minimal/work/i686-linux/flex-native-2.5.35-r5.1/temp/run.do_configure.12240:
> /home/frans/oe/tmp_minimal/sysroots/i686-linux/usr/bin/automake:
> /home/frans/oe/tmp_minimal/sysroots/i686-linux/usr/bin/perl: bad interpreter: No such file or directory
This starts to open up the very large can of worms of stuff that uses
host perl (autotools, etc) and then what happens once perl-native has
been built and installed. I've mentioned this before in
http://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg08445.html
--
Tom Rini
Mentor Graphics Corporation
next parent reply other threads:[~2010-11-21 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1PKA9U-00040x-SY@melo.openembedded.org>
2010-11-21 14:03 ` Tom Rini [this message]
2010-11-21 17:47 ` [oe-commits] Frans Meulenbroeks : flex: added perl to dependencies Frans Meulenbroeks
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=4CE926A8.3000402@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.