On 01/19/2018 06:36 PM, Andrea Galbusera wrote:
This is where I think the configuration is not quite right. Instead of
virtual/libx11, it should say virtual/libgl. And if that dependency cannot
be satisfied, then the x11 option should be altogether disabled in the
distro/local config (in poky mesa provides virtual/libgl). At least that's
how it's configured in many other recipes throughout oe-core.
Can you point to any in particular so I can have a look at the pattern?
Basically anything that mentions 'virtual/libgl' - you can grep the
oe-core layer for it.
b) changing the dependency in that option to virtual/libgl and see what kind
of error you get, if any. I guess this is the right fix after all.
Nope, below change has no effect. The error is the same as in the
original post (missing symbols from X11/Xlib.h)
Before producing any patches, I'd really like you to establish the
difference between working and failing build in a systematic way - we've
all been doing 'shotgun debugging based on guessing' up to now to be
honest. Here's how:
1. Do not make any changes to libepoxy recipe, use it as it is now in
oe-core.
2. Build libepoxy with a default plain-poky config, it should succeed.
Copy the working directory of libepoxy somewhere safe for later comparison.
3. Build libepoxy with raspberry config that makes it fail.
4. Carefully compare the working directory of libepoxy with the one that
you saved. What are the differences? How do the configure and compile
steps differ (particularly the output of meson at do_configure stage,
ninja build files, and compiler flags)? How do the sysroots differ,
particularly in what gets installed to /usr/include? It would be great
to establish the specific root cause of the failure vs success and work
out a fix from there.
Alex
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
