Git/perl build problems
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
| /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
Quoted 16 lines · Jeff Mitchell
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: StartedERROR: 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
Quoted 7 lines
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?
--
Darren
Quoted 18 lines
|
/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 directoryMy 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
[email protected]
https://lists.yoctoproject.org/listinfo/poky
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Quoted 26 lines · Darren Hart
Quoted 16 lines · Jeff Mitchell
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: StartedERROR: Logfile of failure stored in:
/home/jmitchell/yocto/build/tmp/work/i686-linux/git-native-1.7.5.1-r1/temp/log.do_configure.12679Quoted 7 lines
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
Quoted 3 lines
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!
Quoted 22 lines
--
DarrenQuoted 18 lines
|
/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 directoryMy 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
[email protected]
https://lists.yoctoproject.org/listinfo/poky
Quoted 7 lines · Saul Wold
Understood, but not fixed yet!
The workaround at this point is to
"bitbake -c cleansstate autoconf-native automake-native"
Thanks should resolve this issue.
Running that now, seems to be working. Would a simple revision bump to those two packages fix the problem for any others?
Thanks,
Jeff
Quoted 12 lines · Jeff Mitchell
Quoted 7 lines · Saul Wold
Understood, but not fixed yet!
The workaround at this point is to
"bitbake -c cleansstate autoconf-native automake-native"
Thanks should resolve this issue.
Running that now, seems to be working. Would a simple revision bump to those two packages fix the problem for any others?
That's my thought, but this issue is that it now uses the host perl, not any perl built by poky, so I am concerned that it also really need to inherit perlnative and I have not completely tested that yet.
Sau!
Quoted 3 lines
Thanks,
Jeff
Quoted 8 lines · Saul Wold
Quoted 7 lines · Jeff Mitchell
Quoted 6 lines · Saul Wold
Understood, but not fixed yet!
The workaround at this point is to
"bitbake -c cleansstate autoconf-native automake-native"
Quoted 8 lines
Quoted 5 lines
Quoted 1 line
Thanks should resolve this issue.
Running that now, seems to be working. Would a simple revision bump to those two packages fix the problem for any others?
That's my thought, but this issue is that it now uses the host perl, not any perl built by poky, so I am concerned that it also really need to inherit perlnative and I have not completely tested that yet.
No, everything is fine and working as intended and they should not need perl-native. We should have bumped PR in hindsight and still could do so, that would be fine.
Cheers,
Richard
Quoted 14 lines · Richard Purdie
Quoted 13 lines · Saul Wold
Quoted 12 lines · Jeff Mitchell
Quoted 7 lines · Saul Wold
Understood, but not fixed yet!
The workaround at this point is to
"bitbake -c cleansstate autoconf-native automake-native"
Thanks should resolve this issue.
Running that now, seems to be working. Would a simple revision bump to those two packages fix the problem for any others?
Quoted 8 lines
Quoted 3 lines
That's my thought, but this issue is that it now uses the host perl, not any perl built by poky, so I am concerned that it also really need to inherit perlnative and I have not completely tested that yet.
No, everything is fine and working as intended and they should not need perl-native. We should have bumped PR in hindsight and still could do so, that would be fine.
Thanks for that confirmation with all the perl machinations I was not sure which perl those tools should really be using. Given that, if you have not already got a commit for that I will offer one up.
Sau!
Quoted 5 lines
Cheers,
Richard
Quoted 19 lines · Saul Wold
Quoted 18 lines · Richard Purdie
Quoted 16 lines · Saul Wold
Quoted 12 lines · Jeff Mitchell
Quoted 7 lines · Saul Wold
Understood, but not fixed yet!
The workaround at this point is to
"bitbake -c cleansstate autoconf-native automake-native"
Thanks should resolve this issue.
Running that now, seems to be working. Would a simple revision bump to those two packages fix the problem for any others?
That's my thought, but this issue is that it now uses the host perl, not any perl built by poky, so I am concerned that it also really need to inherit perlnative and I have not completely tested that yet.
Quoted 7 lines
Quoted 4 lines
No, everything is fine and working as intended and they should not need perl-native. We should have bumped PR in hindsight and still could do so, that would be fine.
Thanks for that confirmation with all the perl machinations I was not sure which perl those tools should really be using. Given that, if you have not already got a commit for that I will offer one up.
While cleaning and recompiling autoconf-native and automake-native helped with the former issue, I've got two more failing packages: librsvg and avahi.
The former is using /home/jmitchell/yocto/build/tmp/sysroots/i686-linux/usr/bin/glib-mkenums
with the result/home/jmitchell/yocto/build/tmp/sysroots/i686-linux/usr/bin/perl: bad interpreter: No such file or directory
The latter is using (with the same result) /home/jmitchell/yocto/build/tmp/sysroots/i686-linux/usr/bin/intltool-update
The former at least looks like a clean/rebuild of glib-2.0 should work -- but it didn't. What's the proper package that needs to be cleaned/rebuilt?
Thanks,
Jeff
Quoted 32 lines · Jeff Mitchell
Quoted 19 lines · Saul Wold
Quoted 18 lines · Richard Purdie
Quoted 16 lines · Saul Wold
Quoted 12 lines · Jeff Mitchell
Quoted 7 lines · Saul Wold
Understood, but not fixed yet!
The workaround at this point is to
"bitbake -c cleansstate autoconf-native automake-native"
Thanks should resolve this issue.
Running that now, seems to be working. Would a simple revision bump to those two packages fix the problem for any others?
That's my thought, but this issue is that it now uses the host perl, not any perl built by poky, so I am concerned that it also really need to inherit perlnative and I have not completely tested that yet.
Quoted 7 lines
Quoted 4 lines
No, everything is fine and working as intended and they should not need perl-native. We should have bumped PR in hindsight and still could do so, that would be fine.
Thanks for that confirmation with all the perl machinations I was not sure which perl those tools should really be using. Given that, if you have not already got a commit for that I will offer one up.
While cleaning and recompiling autoconf-native and automake-native helped with the former issue, I've got two more failing packages:
librsvg and avahi.
Quoted 6 lines
The former is using
/home/jmitchell/yocto/build/tmp/sysroots/i686-linux/usr/bin/glib-mkenumswith the result
/home/jmitchell/yocto/build/tmp/sysroots/i686-linux/usr/bin/perl: bad
interpreter: No such file or directory
Hrm, I haven't seen this myself. Are you still blocked on this?
If so, have you tried a cleanall of autoconf and automake (not the -native versions). Just a stab in the dark...
--
Darren
Quoted 10 lines
The latter is using (with the same result)
/home/jmitchell/yocto/build/tmp/sysroots/i686-linux/usr/bin/intltool-updateThe former at least looks like a clean/rebuild of glib-2.0 should work -- but it didn't. What's the proper package that needs to be cleaned/rebuilt?
Thanks,
Jeff
Signature · 3 lines
Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel
Quoted 4 lines · Darren Hart
Hrm, I haven't seen this myself. Are you still blocked on this?
If so, have you tried a cleanall of autoconf and automake (not the -native versions). Just a stab in the dark...
I'm not still blocked because having heard nothing I kicked off a full rebuild :-)
Thanks though.
--Jeff
Quoted 11 lines · Jeff Mitchell
While cleaning and recompiling autoconf-native and automake-native helped with the former issue, I've got two more failing packages:
librsvg and avahi.The former is using
/home/jmitchell/yocto/build/tmp/sysroots/i686-linux/usr/bin/glib-mkenumswith the result
/home/jmitchell/yocto/build/tmp/sysroots/i686-linux/usr/bin/perl: bad
interpreter: No such file or directory
Quoted 6 lines
The latter is using (with the same result)
/home/jmitchell/yocto/build/tmp/sysroots/i686-linux/usr/bin/intltool-updateThe former at least looks like a clean/rebuild of glib-2.0 should work -- but it didn't. What's the proper package that needs to be cleaned/rebuilt?
Hi Jeff,
I guess you should rebuild glib-2.0-native rather than glib-2.0?
Or, can you bump bump the PR in the glib-2.0 recipe and try again? I suppose this should work for you.
Looks we should also rebuild intltool-native.
I'll do a complete research and try to figure out all the recipes that needs to be rebuilt and bump the PRs.
Thanks,
-- Dexuan
Quoted 24 lines · Dexuan
Quoted 11 lines · Jeff Mitchell
While cleaning and recompiling autoconf-native and automake-native helped with the former issue, I've got two more failing packages:
librsvg and avahi.The former is using
/home/jmitchell/yocto/build/tmp/sysroots/i686-linux/usr/bin/glib-mkenumswith the result
/home/jmitchell/yocto/build/tmp/sysroots/i686-linux/usr/bin/perl: bad
interpreter: No such file or directoryQuoted 6 lines
The latter is using (with the same result)
/home/jmitchell/yocto/build/tmp/sysroots/i686-linux/usr/bin/intltool-updateThe former at least looks like a clean/rebuild of glib-2.0 should work -- but it didn't. What's the proper package that needs to be cleaned/rebuilt?
Hi Jeff,
I guess you should rebuild glib-2.0-native rather than glib-2.0? Or, can you bump bump the PR in the glib-2.0 recipe and try again? I suppose this should work for you.
Quoted 4 lines
Looks we should also rebuild intltool-native.
I'll do a complete research and try to figure out all the recipes that needs to be rebuilt and bump the PRs.
Hi, I worked out a patch:
http://git.pokylinux.org/cgit/cgit.cgi/poky-contrib/commit/?h=dcui/bump_PR&id=be638790e41206ed740aec69a8704fe77d1bc0b2
and will send it to the oe-core mailing list.
Thanks,
-- Dexuan