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

Fri Jan 25 05:41:11 PST 2013

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"
> > autoreconf: Entering directory `.'
> > autoreconf: configure.ac: not using Gettext
> > autoreconf: running: aclocal --force
> > autoreconf: configure.ac: tracing
> > autoreconf: running: libtoolize --copy --force
> > libtoolize: putting auxiliary files in `.'.
> > libtoolize: copying file `./ltmain.sh'
> > libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
> > libtoolize: rerunning libtoolize, to keep the correct libtool macros
> > in-tree.
> > libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> > autoreconf: running: /usr/bin/autoconf --force
> > autoreconf: running: /usr/bin/autoheader --force
> > autoreconf: running: automake --add-missing --copy --force-missing
> > autoreconf: Leaving directory `.'
> > checking for a BSD-compatible install... /usr/bin/install -c
> > checking whether build environment is sane... yes
> > checking for a thread-safe mkdir -p... /bin/mkdir -p
> > checking for gawk... no
> > checking for mawk... mawk
> > checking whether make sets $(MAKE)... yes
> > checking whether make supports nested variables... yes
> > checking for gcc... gcc
> > checking whether the C compiler works... yes
> > checking for C compiler default output file name... a.out
> > checking for suffix of executables...
> > checking whether we are cross compiling... no
> > checking for suffix of object files... o
> > checking whether we are using the GNU C compiler... yes
> > checking whether gcc accepts -g... yes
> > checking for gcc option to accept ISO C89... none needed
> > checking for style of include used by make... GNU
> > checking dependency style of gcc... gcc3
> > checking for g++... g++
> > checking whether we are using the GNU C++ compiler... yes
> > checking whether g++ accepts -g... yes
> > checking dependency style of g++... gcc3
> > checking for a sed that does not truncate output... /bin/sed
> > checking build system type... armv6l-unknown-linux-gnueabihf
> > checking host system type... armv6l-unknown-linux-gnueabihf
> > checking how to print strings... printf
> > checking for a sed that does not truncate output... (cached) /bin/sed
> > checking for grep that handles long lines and -e... /bin/grep
> > checking for egrep... /bin/grep -E
> > checking for fgrep... /bin/grep -F
> > checking for ld used by gcc... /usr/bin/ld
> > checking if the linker (/usr/bin/ld) is GNU ld... yes
> > checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> > checking the name lister (/usr/bin/nm -B) interface... BSD nm
> > checking whether ln -s works... yes
> > checking the maximum length of command line arguments... 1572864
> > checking whether the shell understands some XSI constructs... yes
> > checking whether the shell understands "+="... yes
> > checking how to convert armv6l-unknown-linux-gnueabihf file names to
> > armv6l-unknown-linux-gnueabihf format... func_convert_file_noop
> > checking how to convert armv6l-unknown-linux-gnueabihf file names to
> > toolchain format... func_convert_file_noop
> > checking for /usr/bin/ld option to reload object files... -r
> > checking for objdump... objdump
> > checking how to recognize dependent libraries... pass_all
> > checking for dlltool... no
> > checking how to associate runtime and link libraries... printf %s\n
> > checking for ar... ar
> > checking for archiver @FILE support... @
> > checking for strip... strip
> > checking for ranlib... ranlib
> > checking command to parse /usr/bin/nm -B output from gcc object... ok
> > checking for sysroot... no
> > checking for mt... mt
> > checking if mt is a manifest tool... no
> > checking how to run the C preprocessor... gcc -E
> > checking for ANSI C header files... yes
> > checking for sys/types.h... yes
> > checking for sys/stat.h... yes
> > checking for stdlib.h... yes
> > checking for string.h... yes
> > checking for memory.h... yes
> > checking for strings.h... yes
> > checking for inttypes.h... yes
> > checking for stdint.h... yes
> > checking for unistd.h... yes
> > checking for dlfcn.h... yes
> > checking for objdir... .libs
> > checking if gcc supports -fno-rtti -fno-exceptions... no
> > checking for gcc option to produce PIC... -fPIC -DPIC
> > checking if gcc PIC flag -fPIC -DPIC works... yes
> > checking if gcc static flag -static works... yes
> > checking if gcc supports -c -o file.o... yes
> > checking if gcc supports -c -o file.o... (cached) yes
> > checking whether the gcc linker (/usr/bin/ld) supports shared
> > libraries... yes
> > checking whether -lc should be explicitly linked in... no
> > checking dynamic linker characteristics... GNU/Linux ld.so
> > checking how to hardcode library paths into programs... immediate
> > checking whether stripping libraries is possible... yes
> > checking if libtool supports shared libraries... yes
> > checking whether to build shared libraries... yes
> > checking whether to build static libraries... no
> > checking how to run the C++ preprocessor... g++ -E
> > checking for ld used by g++... /usr/bin/ld
> > checking if the linker (/usr/bin/ld) is GNU ld... yes
> > checking whether the g++ linker (/usr/bin/ld) supports shared
> > libraries... yes
> > checking for g++ option to produce PIC... -fPIC -DPIC
> > checking if g++ PIC flag -fPIC -DPIC works... yes
> > checking if g++ static flag -static works... yes
> > checking if g++ supports -c -o file.o... yes
> > checking if g++ supports -c -o file.o... (cached) yes
> > checking whether the g++ linker (/usr/bin/ld) supports shared
> > libraries... yes
> > checking dynamic linker characteristics... (cached) GNU/Linux ld.so
> > checking how to hardcode library paths into programs... immediate
> > checking for pkg-config... /usr/bin/pkg-config
> > checking pkg-config is at least version 0.9.0... yes
> > checking for dlopen... no
> > checking for dlopen in -ldl... yes
> > checking execinfo.h usability... yes
> > checking execinfo.h presence... yes
> > checking for execinfo.h... yes
> > checking for mkostemp... yes
> > checking for strchrnul... yes
> > 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?
> 
> 
> Thanks,
> pq
> _______________________________________________
> Wayland-bugs mailing list
> Wayland-bugs at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/wayland-bugs

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.

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?

Thank you
jk

P.S.: The instructions I meant were these: http://wayland.freedesktop.org/raspberrypi.html