./autogen.sh fails on ChromeOS
superloach opened this issue · 8 comments
I'm using Chromebrew, by the way.
bash-4.3$ pwd
/usr/local/tmp/crew/v1.3.tar.gz.dir/xcb-util-xrm-1.3
bash-4.3$ ls
autogen.sh configure.ac COPYING Doxyfile include m4 Makefile.am README src tests
xcb_xrm_intro.in xcb-xrm.pc.in
bash-4.3$ ./autogen.sh
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal -I m4
/usr/local/share/aclocal/aalib.m4:12: warning: underquoted definition of AM_PATH_AALIB
/usr/local/share/aclocal/aalib.m4:12: run info Automake 'Extending aclocal'
/usr/local/share/aclocal/aalib.m4:12: or see https://www.gnu.org/software/automake/manual/automake.html#Extending-aclocal
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/local/bin/autoconf
autoreconf: configure.ac: not using Autoheader
autoreconf: running: automake --add-missing --copy --no-force
configure.ac:10: installing './compile'
configure.ac:12: installing './install-sh'
configure.ac:12: installing './missing'
Makefile.am:24: error: Libtool library used but 'LIBTOOL' is undefined
Makefile.am:24: The usual way to define 'LIBTOOL' is to add 'LT_INIT'
Makefile.am:24: to 'configure.ac' and run 'aclocal' and 'autoconf' again.
Makefile.am:24: If 'LT_INIT' is in 'configure.ac', make sure
Makefile.am:24: its definition is in aclocal's search path.
Makefile.am: installing './depcomp'
Makefile.am:35: error: 'pkgconfig_DATA' is used but 'pkgconfigdir' is undefined
Makefile.am:26: error: 'xcbinclude_HEADERS' is used but 'xcbincludedir' is undefined
parallel-tests: installing './test-driver'
autoreconf: automake failed with exit status: 1
I can confirm that gettext, autoconf, automake, libtool, pkgconfig, and xcb_util are installed.
Did you run git submodule update --init first?
This is in the release .tar.gz, due to how Chromebrew packages work. What dependencies would be pulled by git submodule update --init?
It'd pull the m4 package. Frankly, I'm not very versed in autotools. The build setup here was taken 1:1 from similar xcb tools. I think #77 was the same issue, but they solved it in a different way.
I see. We already have m4, so perhaps it's the wrong version?
Aha, I figured it out! I had to use the actual release, rather than the source code. 🤦♀️
Thanks for your tips though, hopefully I can get i3 working soon!
Ah, yeah, I figured you were using the correct one. I don't think Github let's me remove those automatic ones. So we can close this then? :)
Yes, sorry about that.
No worries, I'll take it over having to fix something. ;)