entao velox256, no site que citei acima, havia uma orientação pra seguir estes procedimentos
mkdir openchrome
cd openchrome
svn co http://svn.openchrome.org/svn/trunk
cd trunk
./autogen.sh
make
make install
git-clone git://anongit.freedesktop.org/git/mesa/drm
cd drm
./autogen.sh
make
make install
cd linux-core
make LINUXDIR=/lib/modules/`uname -r`/build DRM_MODULES=via
cp *.ko /lib/modules/`uname -r`/kernel/drivers/char/drm/
depmod -ae mas quando chego na linha
./autogen.sh, la da primeira parte ainda, eis o que acontece
root@esteves:/home/esteves/openchrome/trunk# ./autogen.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf
autoreconf: running: /usr/bin/autoheader
autoreconf: running: automake --add-missing --copy --no-force
libxvmc/Makefile.am:2: Libtool library used but `LIBTOOL' is undefined
libxvmc/Makefile.am:2: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
libxvmc/Makefile.am:2: to `configure.ac' and run `aclocal' and `autoconf' again.
libxvmc/Makefile.am:2: If `AC_PROG_LIBTOOL' is in `configure.ac', make sure
libxvmc/Makefile.am:2: its definition is in aclocal's search path.
src/Makefile.am:31: Libtool library used but `LIBTOOL' is undefined
src/Makefile.am:31: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/Makefile.am:31: to `configure.ac' and run `aclocal' and `autoconf' again.
src/Makefile.am:31: If `AC_PROG_LIBTOOL' is in `configure.ac', make sure
src/Makefile.am:31: its definition is in aclocal's search path.
autoreconf: automake failed with exit status: 1
e sou obrigado a parar ali, porque se eu tentar o passo seguinte, que é o
make,
da outro erro como mostro aqui..
root@esteves:/home/esteves/openchrome/trunk# make
make: *** Nenhum alvo indicado e nenhum arquivo make encontrado. Pare.