build error
Hello,
I started experimenting with the meta-mingw layer today, using the 'daisy' branch for both, poky as well as meta-mingw.
Running bitbake meta-toolchain, the build process failed in one of the last steps (1003 of 1005) with:
ERROR: nativesdk-packagegroup-sdk-host not found in the base feeds (x86_64-nativesdk-mingw32 noarch any all).
Any idea what I may be missing ? I'm using
MACHINE ??= "qemux86"
SDKMACHINE ?= "x86_64-mingw32"
Thanks,
Stefan
Signature · 3 lines
Stefan Seefeld CodeSourcery / Mentor Embedded http://www.mentor.com/embedded-software/
Quoted 8 lines · Stefan Seefeld
Hello,
I started experimenting with the meta-mingw layer today, using the 'daisy' branch for both, poky as well as meta-mingw.
Running
bitbake meta-toolchain, the build process failed in one of the last steps (1003 of 1005) with:
Quoted 7 lines
ERROR: nativesdk-packagegroup-sdk-host not found in the base feeds (x86_64-nativesdk-mingw32 noarch any all).
Any idea what I may be missing ? I'm using
MACHINE ??= "qemux86"
SDKMACHINE ?= "x86_64-mingw32"
Which pacxkage backend were you using? If you didn't use ipk, I'd suggest trying it. In theory others should work but its ipk I've been using when working with those layers.
Cheers,
Richard
Quoted 12 lines · Richard Purdie
Quoted 11 lines · Stefan Seefeld
Hello,
I started experimenting with the meta-mingw layer today, using the 'daisy' branch for both, poky as well as meta-mingw.
Running
bitbake meta-toolchain, the build process failed in one of the last steps (1003 of 1005) with:ERROR: nativesdk-packagegroup-sdk-host not found in the base feeds (x86_64-nativesdk-mingw32 noarch any all).
Quoted 8 lines
Quoted 4 lines
Any idea what I may be missing ? I'm using
MACHINE ??= "qemux86"
SDKMACHINE ?= "x86_64-mingw32"Which pacxkage backend were you using? If you didn't use ipk, I'd suggest trying it. In theory others should work but its ipk I've been using when working with those layers.
OK, I was using rpm (the default), but now switched to ipk. That results in a different error in meta/lib/oe/sdk.py:55, where do_populate() tries to link ld.so.cache into a non-existent directory.
I have attempted a fix with the attached patch.
With that, things now appear to be working. (I think things should also work with 'rpm' as package backend, though, right ? Should I file a bug report somewhere to put that on record ?)
Thanks,
Stefan
Signature · 3 lines
Stefan Seefeld CodeSourcery / Mentor Embedded http://www.mentor.com/embedded-software/
meta/lib/oe/sdk.py +3 -2
@@ -50,8 +50,9 @@ class Sdk(object): "*.la")) # Link the ld.so.cache file into the hosts filesystem - link_name = os.path.join(self.sdk_output, self.sdk_native_path, - self.sysconfdir, "ld.so.cache") + sysconfdir = os.path.join(self.sdk_output, self.sdk_native_path, self.sysconfdir) + bb.utils.mkdirhier(sysconfdir) + link_name = os.path.join(sysconfdir, "ld.so.cache") os.symlink("/etc/ld.so.cache", link_name) execute_pre_post_process(self.d, self.d.getVar('SDK_POSTPROCESS_COMMAND', True))
Quoted 18 lines · Stefan Seefeld
Quoted 17 lines · Richard Purdie
Quoted 15 lines · Stefan Seefeld
Hello,
I started experimenting with the meta-mingw layer today, using the 'daisy' branch for both, poky as well as meta-mingw.
Running
bitbake meta-toolchain, the build process failed in one of the last steps (1003 of 1005) with:ERROR: nativesdk-packagegroup-sdk-host not found in the base feeds (x86_64-nativesdk-mingw32 noarch any all).
Any idea what I may be missing ? I'm using
MACHINE ??= "qemux86"
SDKMACHINE ?= "x86_64-mingw32"
Quoted 8 lines
Quoted 3 lines
Which pacxkage backend were you using? If you didn't use ipk, I'd suggest trying it. In theory others should work but its ipk I've been using when working with those layers.
OK, I was using rpm (the default), but now switched to ipk. That results in a different error in
meta/lib/oe/sdk.py:55, wheredo_populate()tries to link ld.so.cache into a non-existent directory.
I have attempted a fix with the attached patch.
I think this was fixed on master, there is a patch we need to backport to daisy. I've just done that since I've been aware of that issue.
Quoted 3 lines
With that, things now appear to be working. (I think things should also work with 'rpm' as package backend, though, right ? Should I file a bug report somewhere to put that on record ?)
You can file a bug in the bugzilla for it, yes.
Cheers,
Richard