From: Saul Wold <saul.wold@intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: poky@yoctoproject.org
Subject: Re: Git/perl build problems
Date: Mon, 13 Jun 2011 13:42:25 -0700 [thread overview]
Message-ID: <4DF67631.9000702@intel.com> (raw)
In-Reply-To: <4DF6715D.3050703@linux.intel.com>
On 06/13/2011 01:21 PM, Darren Hart wrote:
> On 06/13/2011 12:44 PM, Jeff Mitchell wrote:
>> Hello,
>>
>> Late last week I did a full rebuild of packages from poky master branch
>> (beagleboard target). Today, if I update my clone's master branch to
>> current upstream, I'm unable to build git (extra whitespace added for
>> clarity)
>>
>> NOTE: Running task 210 of 4247 (ID: 324,
>> virtual:native:/home/jmitchell/yocto/poky/meta/recipes-devtools/git/git_1.7.5.1.bb,
>> do_configure)
>>
>> NOTE: package git-native-1.7.5.1-r1: task do_configure: Started
>>
>> ERROR: Logfile of failure stored in:
>> /home/jmitchell/yocto/build/tmp/work/i686-linux/git-native-1.7.5.1-r1/temp/log.do_configure.12679
>>
>> Log data follows:
>>
>> |
>> /home/jmitchell/yocto/build/tmp/work/i686-linux/git-native-1.7.5.1-r1/temp/run.do_configure.12679:
>> /home/jmitchell/yocto/build/tmp/sysroots/i686-linux/usr/bin/automake:
>> /home/jmitchell/yocto/build/tmp/sysroots/i686-linux/usr/bin/perl: bad
>> interpreter: No such file or directory
>
>
> This is a known issue with a change in the perlnative bits - I hit this
> late last week. I thought this had been fixed. Saul?
>
Understood, but not fixed yet!
The workaround at this point is to
"bitbake -c cleansstate autoconf-native automake-native"
Thanks should resolve this issue.
Sau!
> --
> Darren
>
>> |
>> /home/jmitchell/yocto/build/tmp/work/i686-linux/git-native-1.7.5.1-r1/temp/run.do_configure.12679:
>> /home/jmitchell/yocto/build/tmp/sysroots/i686-linux/usr/bin/automake:
>> /home/jmitchell/yocto/build/tmp/sysroots/i686-linux/usr/bin/perl: bad
>> interpreter: No such file or directory
>>
>> My guess is that it's related to 4c790efa, but reverting that patch in a
>> private branch did not really help. I've tried cleaning and rebuilding
>> perl, perl-native, and git, with no success.
>>
>> Did I simply miss some updating step...?
>>
>> Thanks,
>> Jeff
>> _______________________________________________
>> poky mailing list
>> poky@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
>
next prev parent reply other threads:[~2011-06-13 20:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 19:44 Git/perl build problems Jeff Mitchell
2011-06-13 20:21 ` Darren Hart
2011-06-13 20:42 ` Saul Wold [this message]
2011-06-13 21:04 ` Jeff Mitchell
2011-06-13 21:09 ` Saul Wold
2011-06-13 21:14 ` Richard Purdie
2011-06-13 21:18 ` Saul Wold
2011-06-14 14:54 ` Jeff Mitchell
2011-06-16 21:06 ` Darren Hart
2011-06-16 22:58 ` Jeff Mitchell
2011-06-17 1:24 ` Cui, Dexuan
2011-06-17 2:46 ` Cui, Dexuan
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=4DF67631.9000702@intel.com \
--to=saul.wold@intel.com \
--cc=dvhart@linux.intel.com \
--cc=poky@yoctoproject.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.