quilt-native do_populate_sysroot error
Hi
I needed to re-setup my yocto directory due to a fs error (was using btrfs). Before I used master-next. Now I checked out daisy.
When I start bitbaking, I already get an error ["File not found"] when building quilt-native. The error is in the step do_populate_sysroot. The problem is pretty clear:
run.do_populate_sysroot:
def do_populate_sysroot(d):
bb.build.exec_func("sysroot_stage_all", d)
for f in (d.getVar('SYSROOT_PREPROCESS_FUNCS', True) or '').split():
bb.build.exec_func(f, d)
pn = d.getVar("PN", True)
multiprov = d.getVar("MULTI_PROVIDER_WHITELIST", True).split()
provdir =d.expand("/home/ubuntu/yocto/build/tmp/work/x86_64-linux/quilt-native/0.61-r0/sysroot-destdir//home/ubuntu/yocto/build/tmp/sysroots/x86_64-linux/sysroot-providers/")
bb.utils.mkdirhier(provdir)
for p in d.getVar("PROVIDES", True).split():
if p in multiprov:
continue
p = p.replace("/", "_")
with open(provdir + p, "w") as f:
f.write(pn)
do_populate_sysroot(d)
Well, the provdir variable is definitely wrong!
How should I fix this?
Thanks
Michael
Re: quilt-native do_populate_sysroot error [solved]
This made me crazy, so after lots of tries I thought I should try to do it *without* my own conf files, although I couldn't imagine why my conf files produce such an error.
Before I copied the whole conf dir back from a backup. This time I tried with a completely new conf dir. I did that and strangely got another error message by "sanity-check" saying that I am missing two files (makeinfo, chrpath).
So, I now understand that there is a file called "sanity-check" in the conf folder that is not a config file but a state file, declaring if my installation is complete. As I copied this also in my first attempts, it did no longer check and so the problem that I am missing a tool was not reported.
Now, it seems, everything is working. Nonetheless, I would like to suggest that the sanity-check file should be moved out of the conf folder into the state folder in a future yocto revision.
Cheers
Michael
Am 01.05.2014 12:19, schrieb Neuer User:
Quoted 39 lines
Hi
I needed to re-setup my yocto directory due to a fs error (was using btrfs). Before I used master-next. Now I checked out daisy.
When I start bitbaking, I already get an error ["File not found"] when building quilt-native. The error is in the step
do_populate_sysroot. The problem is pretty clear:run.do_populate_sysroot:
def
do_populate_sysroot(d):
bb.build.exec_func("sysroot_stage_all", d)
for f in (d.getVar('SYSROOT_PREPROCESS_FUNCS', True)or '').split():
bb.build.exec_func(f, d)
pn =d.getVar("PN", True)
multiprov =d.getVar("MULTI_PROVIDER_WHITELIST", True).split()
provdir =d.expand("/home/ubuntu/yocto/build/tmp/work/x86_64-linux/quilt-native/0.61-r0/sysroot-destdir//home/ubuntu/yocto/build/tmp/sysroots/x86_64-linux/sysroot-providers/")
bb.utils.mkdirhier(provdir)
for p ind.getVar("PROVIDES", True).split():
if p in multiprov:
continue
p =p.replace("/", "_")
withopen(provdir + p, "w")as f:
f.write(pn)
do_populate_sysroot(d)Well, the provdir variable is definitely wrong!
How should I fix this?
Thanks
Michael
Re: quilt-native do_populate_sysroot error [solved]
Quoted 4 lines · Neuer User
Before I copied the whole conf dir back from a backup. This time I tried with a completely new conf dir. I did that and strangely got another error message by "sanity-check" saying that I am missing two files (makeinfo, chrpath).
well, conf/ dir is generated when you setup the workspace for firs time and then we do version checks if it needs to be updated. no idea what you backed up but usually keeping
your changes applied on top of regenerated conf/ dir is a better option when you move
from one version of YP release to another
Re: quilt-native do_populate_sysroot error [solved]
Am 02.05.2014 08:43, schrieb Khem Raj:
Quoted 6 lines · Neuer User
Quoted 4 lines
Before I copied the whole conf dir back from a backup. This time I tried with a completely new conf dir. I did that and strangely got another error message by "sanity-check" saying that I am missing two files (makeinfo, chrpath).
Quoted 7 lines
well, conf/ dir is generated when you setup the workspace for firs time and then we do version checks if it needs to be updated. no idea what you backed up but usually keeping
your changes applied on top of regenerated conf/ dir is a better option when you move
from one version of YP release to another
I backup up the whole conf dir, as I wanted to make sure that all configuration is backed up. The problem I see is that the conf dir does not only include configuration data, but also state data, namely the state "system requirements have been checked" (sanity-check).
It seems to be no problem to completely restore the conf dir, when you don't restore this one file.