I've been searching but can't find the answer. I'm currently studying buildroot and it's been great, well until this one.
I'm trying to add Coova Chilli as a package.
here's my .mk file.
#############################################################
#
# coovachilli
#
#############################################################
COOVACHILLI_VERSION = 1.4
COOVACHILLI_SOURCE = $(COOVACHILLI_VERSION).tar.gz
COOVACHILLI_SITE = https://github.com/coova/coova-chilli/archive
COOVACHILLI_INSTALL_STAGING = YES
COOVACHILLI_INSTALL_TARGET = NO
COOVACHILLI_CONF_OPTS = --prefix=/usr --libdir=/usr/lib --localstatedir=/var --sysconfdir=/etc --enable-miniportal --with-openssl --enable-libjson --enable-useragent --enable-sessionstate --enable-sessionid --enable-chilliredir --enable-binstatusfile --enable-statusfile --disable-static --enable-shared --enable-largelimits --enable-proxyvsa --enable-chilliproxy --enable-chilliradsec --with-poll --enable-dhcpopt --enable-sessgarden --enable-ipwhitelist --enable-redirdnsreq --enable-miniconfig --enable-layer3 --enable-chilliscript --enable-eapol --enable-uamdomainfile --enable-modules --enable-multiroute
COOVACHILLI_DEPENDENCIES = openssl make libtool
$(eval $(autotools-package))
been following some tutorials and also this one.
But whatever I do, with this package included I always end up with:
/bin/bash: ./configure: No such file or directory
I have tried deselecting this package and the make is successful.
I'm stuck on >>> coovachilli 1.4 Configuring part with that error.
I've check the buildroot > dl folder and can see that it successfully downloaded the file.
Also on buildroot > output > build I can see coovachilli-1.4 folder with the files in it.
But whatever I do, with this package included I always end up with:
/bin/bash: ./configure: No such file or directory
That would appear to be because the tarball you're using indeed does not contain a configure script. The project's GitHub source repository and the release tarballs available from there do not contain one, nor various other Autotools-generated files, but instead provide a "bootstrap" script that runs the Autotools to produce them.
That approach follows a philosophy of not committing derived files to the source repository, but that's a somewhat simplistic analysis with respect to the Autotools because
One of the key design points of the Autotools is that they are tools for package maintainers, not for people who merely want to build the package. Running the Autotools is not intended to be a normal part of the build process.
Accordingly, distribution packages built by Automake-based build systems do include all the generated files constituting the build system. Third party tools that expect you to hand them an Autotools-based distribution package are right to expect those to be included.
Furthermore, the scripts and other files generated by the Autotools are more portable than the Autotools input files from which they are generated. In particular, Autotools inputs are not always fully compatible with different versions of the Autotools than they were written for.
Anyway, supposing that you use the tarball provided by GitHub, you need to run the bootstrap script between unpacking it and launching into configure. Do note that from a buildroot perspective, this introduces dependencies on (at least) Autoconf and Automake into your build.