On Sat, 10 Dec 2016 22:09:29 +0330 Ali <[email protected]> wrote: > Dear Wayland, > > After I’ve read “Building Weston” doc I cross compiled the wayland and then I > tried to run Weston by : > start-weston > > It complained: > > [00:01:00.878] weston 1.0.3 > http://wayland.freedesktop.org/ > Bug reports to: > https://bugs.freedesktop.org/enter_bug.cgi?product=weston > Build: > [00:01:00.878] OS: Linux, 3.0.35, #3 SMP PREEMPT Tue Nov 15 09:36:14 MST > 2016, armv7l > [00:01:00.883] Loading module '/usr/lib/weston/gal2d-backend.so' > [00:01:01.031] input device unknown, /dev/input/mice ignored: unsupported > device type > [00:01:01.191] Loading module '/usr/lib/weston/desktop-shell.so' > [00:01:01.199] libwayland: using socket /tmp_weston/wayland-0 > [00:01:01.200] launching '/usr/libexec/weston-desktop-shell' > /usr/libexec/weston-desktop-shell: symbol lookup error: > /usr/lib/libwayland-cursor.so.0: undefined symbol: > wl_proxy_marshal_constructor
Hi, this happens when you have built libwayland-cursor with a wayland-scanner version that is higher than the libwayland-client you built or are using at runtime. It is recommended to always have wayland-scanner exactly the same version as the libwayland you are building and running. It is ok to use an older wayland-scanner than the libwayland you are running, but the opposite is not guaranteed to work so far. Thanks, pq
pgpa46SeJ3PT3.pgp
Description: OpenPGP digital signature
_______________________________________________ wayland-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/wayland-devel
