Not able to build Weston.

[Srivardhan M S]

Hi Pekka,

Thank you very much, Setting the path resolved the issue.

Thanks Bryce for the build commands. I was able to build the weston.

Thank-you,
Sri

On Wed, Apr 2, 2014 at 11:52 AM, Pekka Paalanen <ppaalanen at gmail.com> wrote:
> On Wed, 2 Apr 2014 10:36:56 +0530
> Srivardhan M S <srivardhanms at gmail.com> wrote:
>
>> Hi,
>>
>> I repeated the steps, but am getting the same issue. :( Below is the log:
>> sri.hebbar at sri-hebbar:~/Wayland/weston$ git clean -xfd
>> Removing Makefile
>> Removing Makefile.in
>> Removing aclocal.m4
>> Removing autom4te.cache/
>> Removing build-aux/
>> Removing clients/.deps/
>> Removing config.h
>> Removing config.h.in
>> Removing config.log
>> Removing config.status
>> Removing configure
>> Removing desktop-shell/.deps/
>> Removing libtool
>> Removing protocol/.deps/
>> Removing protocol/screenshooter-protocol.c
>> Removing protocol/screenshooter-server-protocol.h
>> Removing protocol/text-cursor-position-protocol.c
>> Removing shared/.deps/
>> Removing src/.deps/
>> Removing src/version.h
>> Removing src/weston.pc
>> Removing stamp-h1
>> Removing tests/.deps/
>> Removing wcap/.deps/
>> Removing xwayland/.deps/
>> sri.hebbar at sri-hebbar:~/Wayland/weston$  ./autogen.sh --prefix=$WLD
>> --with-cairo=gl --enable-setuid-install=no \
>> >         --enable-clients \
>> >         --enable-headless-compositor \
>> >         --enable-demo-clients-install
>> autoreconf: Entering directory `.'
>> autoreconf: configure.ac: not using Gettext
>> autoreconf: running: aclocal -I /home/sri.hebbar/install/share/aclocal --force
>> autoreconf: configure.ac: tracing
>> autoreconf: configure.ac: creating directory build-aux
>> autoreconf: running: libtoolize --install --copy --force
>> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `build-aux'.
>> libtoolize: copying file `build-aux/config.guess'
>> libtoolize: copying file `build-aux/config.sub'
>> libtoolize: copying file `build-aux/install-sh'
>> libtoolize: copying file `build-aux/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
>> configure.ac:25: installing `build-aux/missing'
>> Makefile.am: installing `build-aux/depcomp'
>> autoreconf: Leaving directory `.'
>> 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 how to run the C preprocessor... gcc -E
>> checking for grep that handles long lines and -e... /bin/grep
>> checking for egrep... /bin/grep -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 minix/config.h usability... no
>> checking minix/config.h presence... no
>> checking for minix/config.h... no
>> checking whether it is safe to define __EXTENSIONS__... yes
>> checking for special C compiler options needed for large files... no
>> checking for _FILE_OFFSET_BITS value needed for large files... 64
>> 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 for style of include used by make... GNU
>> checking dependency style of gcc... gcc3
>> checking whether make supports nested variables... yes
>> checking for gcc... (cached) gcc
>> checking whether we are using the GNU C compiler... (cached) yes
>> checking whether gcc accepts -g... (cached) yes
>> checking for gcc option to accept ISO C89... (cached) none needed
>> checking for a sed that does not truncate output... /bin/sed
>> checking build system type... i686-pc-linux-gnu
>> checking host system type... i686-pc-linux-gnu
>> checking how to print strings... printf
>> checking for a sed that does not truncate output... (cached) /bin/sed
>> 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 i686-pc-linux-gnu file names to
>> i686-pc-linux-gnu format... func_convert_file_noop
>> checking how to convert i686-pc-linux-gnu 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 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 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 whether SFD_CLOEXEC is declared... yes
>> checking whether TFD_CLOEXEC is declared... yes
>> checking whether CLOCK_MONOTONIC is declared... 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 initgroups... yes
>> checking for posix_fallocate... yes
>> checking for EGL... yes
>> checking for EGL_TESTS... yes
>> checking for XWAYLAND... yes
>> checking for XWAYLAND_TEST... yes
>> checking for LIBDRM... yes
>> checking for XCB... yes
>> checking for xcb_poll_for_queued_event... yes
>> checking for X11_COMPOSITOR_XKB... no
>> checking for X11_COMPOSITOR... yes
>> checking for DRM_COMPOSITOR... yes
>> checking for COMPOSITOR... yes
>> checking for WAYLAND_COMPOSITOR... yes
>> checking for RPI_COMPOSITOR... yes
>> checking for RPI_BCM_HOST... no
>> configure: WARNING: Raspberry Pi BCM host libraries not found, will
>> use stubs instead.
>> checking for FBDEV_COMPOSITOR... yes
>> checking for PIXMAN... yes
>> checking for PNG... yes
>> checking for WEBP... no
>> checking for LIBVA... no
>> checking for jpeg_CreateDecompress in -ljpeg... yes
>> checking for CAIRO... yes
>> checking for TEST_CLIENT... yes
>> checking for SIMPLE_CLIENT... yes
>> checking for SIMPLE_EGL_CLIENT... yes
>> checking for CLIENT... yes
>> checking for SERVER... yes
>> checking for WESTON_INFO... yes
>> checking for CAIRO_EGL... yes
>> checking for PANGO... no
>> checking for SYSTEMD_LOGIN... no
>> checking for SYSTEMD_LOGIN_209... no
>> checking for pam_open_session in -lpam... yes
>> checking for GLU... no
>> checking for COLORD... no
>> checking for DBUS... no
>> checking for WCAP... yes
>> checking for SETBACKLIGHT... yes
>> checking for LIBUNWIND... yes
>> configure: Weston's native backend: drm-backend.so
>> configure: Weston's default desktop shell client: weston-desktop-shell
>> checking for LCMS... no
>> checking for wayland-scanner... /usr/bin/wayland-scanner
>
> Are you sure /usr/bin/wayland-scanner is the one you built from
> wayland, and not some ancient version provided by your distribution?
>
>> sri.hebbar at sri-hebbar:~/Wayland/weston$ make install
>>   GEN    protocol/screenshooter-protocol.c
>>   GEN    protocol/screenshooter-server-protocol.h
>>   GEN    protocol/text-cursor-position-protocol.c
>> <stdin>:6: unknown type
>> make: *** [protocol/text-cursor-position-protocol.c] Error 1
>
> I see that http://wayland.freedesktop.org/building.html does not tell
> you to set PATH so that the wayland-scanner you built would be found
> automatically.
>
> There is a pkg-config file that provides the right path:
>
> $ pkg-config --variable=wayland_scanner wayland-scanner
> /home/pq/local/bin/wayland-scanner
>
> but looking at configure.ac, I don't think it gets used:
>
> AC_PATH_PROG([wayland_scanner], [wayland-scanner])
> if test x$wayland_scanner = x; then
>         AC_MSG_ERROR([wayland-scanner is needed to compile weston])
> fi
>
> PKG_CHECK_MODULES(WAYLAND_SCANNER, wayland-scanner)
>
> I think something here would need to be fixed, but your personal issue
> can probably be fixed by setting PATH right.
>
>
> Thanks,
> pq