Config bug in wayland

[Pekka Paalanen]

On Tue, 13 May 2014 18:04:07 -0700
Bill Spitzak <spitzak at gmail.com> wrote:

> Trying to replicate my success at building Wayland, starting from 
> scratch, I found an error at the first step if $ALOCAL is exported as 
> stated, and no install has ever been done:
> 
> ~/Wayland/wayland$ ./autogen.sh --prefix=$WLD
> autoreconf: Entering directory `.'
> autoreconf: configure.ac: not using Gettext
> autoreconf: running: aclocal -I /home/wspitzak/install/share/aclocal 
> --force -I m4 ${ACLOCAL_FLAGS}
> aclocal: couldn't open directory `/home/wspitzak/install/share/aclocal': 
> No such file or directory
> autoreconf: aclocal failed with exit status: 1
> 
> I fixed it with "mkdir -r $WLD/share/aclocal". But since "make install" 
> actually creates this directory, wayland conf probably should not 
> require it.

Just like it says in your error message, it is 'aclocal' itself, part of
automake utilities, requiring the directory to exist. I don't think we
can fix it in wayland code base apart from doing 'mkdir -p
$ACLOCAL_PATH' in autogen.sh and I don't know if that would be ok.

If you want to fix the website, you can find it in git:
http://cgit.freedesktop.org/wayland/wayland-web/
The patch submission process is the same as for Wayland and Weston.

- pq