Short update: It appears I have two machines where the configure script find wayland-scanner in /usr/bin and one machine where it actually find the correct one in the sysroot. The difference seems to be that the machine where it works doesn't have a wayland-scanner in /usr/bin/, for some reason the one in /usr/bin gets chosen before the sysroot version when available.
Cheers, Erik On Wed, Jul 2, 2014 at 9:48 AM, Erik Botö <[email protected]> wrote: > Hi, > > I noticed differences when building mesa on my local machine and on > one of our build servers. It failed on my local host due to errors in > the generated wayland-drm-client-protocol.h but worked on the build > server. Examining log.do_compile I noticed that it uses > wayland-scanner from /usr/bin/ on both machines instead of using the > one present in the sysroot, so I guess it works due to luck on one > machine. > > If I make /usr/bin/wayland-scanner a symlink to the version in the > sysroot it builds ok. > > Can anyone else verify if their mesa builds uses the hosts > wayland-scanner? And does anyone the proper way to convince mesa to > use the sysroot version? > > (I'm using daisy, so mesa 9.2.5) > > Cheers, > Erik -- Erik Botö M.Sc.E.E. SENIOR SOFTWARE ENGINEER Pelagicore AB Ekelundsgatan 4, 6tr, SE-411 18 Gothenburg, Sweden Mobile: +46 (0)768 817 203 E-Mail: [email protected] PELAGICORE Experience Change -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
