[Wayland-bugs] Weston on Raspberry Pi - Autogen error

[Pekka Paalanen]

On Fri, 25 Jan 2013 14:41:11 +0100
I-tek <i-tek at web.de> wrote:

> On Fri, 25 Jan 2013 09:33:17 +0200
> Pekka Paalanen <ppaalanen at gmail.com> wrote:
> 
> > On Thu, 24 Jan 2013 21:47:43 +0100
> > I-tek <i-tek at web.de> wrote:
> > 
> > > Hello,
> > > 
> > > I have been trying to build wayland, libxkbcommon and weston on
> > > raspberry pi following these instructions quite strictly but I am
> > > experiencing the same Bug over and over again.
> > > wayland and libxkbcommon are no problem but when it comes to weston the
> > > following occurs:
> > > 
> > > pi at raspberrypi:~/weston$ ./autogen.sh --prefix=$WLD
> > > --disable-setuid-install --with-cairo-glesv2 --disable-x11-compositor
> > > --disable-drm-compositor --disable-android-compositor
> > > --disable-wayland-compositor --disable-weston-launch
> > > --disable-simple-egl-clients WESTON_NATIVE_BACKEND="rpi-backend.so"
...
> > > checking for COMPOSITOR... yes
> > > checking for XWAYLAND... yes
> > > checking for RPI_COMPOSITOR... yes
> > > checking for RPI_BCM_HOST... yes
> > > checking for PIXMAN... yes
> > > checking for PNG... yes
> > > checking for WEBP... no
> > > checking for jpeg_CreateDecompress in -ljpeg... yes
> > > checking for CAIRO... yes
> > > checking for SIMPLE_CLIENT... yes
> > > checking for CLIENT... yes
> > > checking for WESTON_INFO... yes
> > > checking for POPPLER... no
> > > checking for CAIRO_EGL... no
> > > configure: WARNING: clients will use cairo image, cairo-egl not used
> > > because No package 'wayland-egl' found
> > > No package 'cairo-egl' found
> > > No package 'cairo-glesv2' found
> > > checking for GLU... no
> > > checking for WCAP... yes
> > > checking for rsvg-convert... no
> > > checking for SETBACKLIGHT... no
> > > configure: Weston's native backend: rpi-backend.so
> > > ./configure: line 18386: syntax error near unexpected token
> > > `'$(top_srcdir)/protocol''
> > > ./configure: line 18386: `WAYLAND_SCANNER_RULES('$(top_srcdir)/protocol')'
> > > 
> > > Is anyone getting the same errors or am I doing something wrong?
> > 
> > Did you forget ACLOCAL from the environment?
> > This seems to be a popular problem recently, there was one case in irc
> > and another in
> > http://lists.freedesktop.org/archives/wayland-devel/2013-January/007068.html
> > 
> > Is there perhaps a build guide out there, which forgets ACLOCAL?
> 
> Moi,
> 
> it was my mistake. I have an environment script and have forgotten that I commented out the ACLOCAL line thus it would use ´aclocal --force´ command. That was because wayland, libxkbcommon nor weston built with the environment variable set.
> 

That would be the first error. Why did they fail?
You may have to

$ mkdir -p $WLD/share/aclocal

first to have aclocal not error out.

The wayland build should install a file into $WLD/share/aclocal that
other builds will then use. That file defines the
WAYLAND_SCANNER_RULES macro, which then gets replaced away when
producing 'configure'. If the file is missing, replacement is not
done, and you get the error you originally posted.

> I am always getting this error:
>   pi at raspberrypi ~/wayland $ ./autogen.sh --prefix=$WLD --disable-documentation
>   autoreconf: Entering directory `.'
>   autoreconf: configure.ac: not using Gettext
>   autoreconf: running: aclocal -I /home/pi/local/share/aclocal -I m4 ${ACLOCAL_FLAGS} --output=aclocal.m4t
>   sh: 1: aclocal -I /home/pi/local/share/aclocal: not found
>   autoreconf: aclocal -I /home/pi/local/share/aclocal failed with exit status: 127
> 
> I don't know what might be the point... Did I miss a dependency?

Looks like you need to fix your environment setup script, if I can
trust the paste above. The spaces in
'aclocal -I /home/pi/local/share/aclocal' are not real spaces, they
are some blank utf-8 characters and mess up the command.


Thanks,
pq