Have this bug been resolved? I'm facing the same error with
"warrior:6d2e12e79211b31cdf5ea824fb9a8be54ba9a9eb" and capstone 4.0.1.
Although in this case I can not see any include path being used in the logs.
On 6/14/18 11:50 PM, Khem Raj wrote:
On Thu, Jun 14, 2018 at 1:08 PM Jon Szymaniak <jon.szyman...@gmail.com
<mailto:jon.szyman...@gmail.com>> wrote:
On Thu, Jun 14, 2018 at 14:18 Khem Raj <raj.k...@gmail.com
<mailto:raj.k...@gmail.com>> wrote:
On Thu, Jun 14, 2018 at 9:56 AM Jon Szymaniak
<jon.szyman...@gmail.com <mailto:jon.szyman...@gmail.com>> wrote:
>
> On Thu, Jun 14, 2018 at 11:43 Khem Raj <raj.k...@gmail.com
<mailto:raj.k...@gmail.com>> wrote:
> > Do you have capstone development headers/libs installed on
your build host ?
> >
>
> No, and I understand that's an easy thing to address on the
build host.
>
> However, I don't think this should be necessary build host
dependency.
> QEMU includes the capstone codebase as a git submodule, so
everything
> that's needed is there.
>
> Maybe it's just a matter of tweaking the recipe to set
> CMAKE_INSTALL_PREFIX appropriately so that when the build
dives down
> into the capstone directory, this points to the correct prefix?
>
> It looks like the inclusion and use of capstone is new, as
of the QEMU
> version included with sumo. (i.e. This appears not to be the
situation
> with the version used in rocko and pyro).
Least intrusive approach would be to disable it if its not
something you
depend on.
Makes sense, thank you.
Two workarounds that worked for me were either adding qemu-native
to ASSUME_PROVIDED or appending “--disable-capstone” to qemu’s
EXTRA_OECONF.
The fact that not everyone sees this issue makes me think that it
might be something in your environment that’s triggering this but if
we disable it then we make the issue irrelevant
I’ll try to follow up with a patch to the recipe in oe-core,
unless you suspect that the source of this is merely something on
my end.
--
Avís -
Aviso - Legal Notice - (LOPD) - http://legal.ifae.es
<http://legal.ifae.es/>
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
