On Github, a large number of projects name their tag vXYZ (i.e v3.0,
v0.1, etc.). In some packages we do:
<pkg>_VERSION = v0.3
<pkg>_SITE = $(call github foo,bar,$(<pkg>_VERSION))
And in some other packages we do:
<pkg>_VERSION = 0.3
<pkg>_SITE = $(call github foo,bar,v$(<pkg>_VERSION))
I.e in one case we consider the version to be v0.3, in the other case
we consider 0.3 to be the version.
The problem with v0.3 is that when used in conjunction with
release-monitoring.org, it doesn't work very well, because
release-monitoring.org has the concept of "version prefix" and using
that they drop the "v" prefix for the version.
Therefore, a number of packages in Buildroot have a version that
doesn't match with release-monitoring.org because Buildroot has 'v0.3'
and release-monitoring.org has '0.3'.
Since really the version number of 0.3, is makes sense to update our
packages to drop this 'v'.
This commit only addresses the (common) case of github packages where
the prefix is simply 'v'. Other cases will be handled by separate
commits. Also, there are a few cases that couldn't be handled
mechanically that aren't covered by this commit.
Signed-off-by: Victor Huesca <victor.huesca@bootlin.com>
[Arnout: don't change flatbuffers, json-for-modern-cpp, libpagekite,
python-scapy3k, softether]
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
liquid-dsp has the following code:
So, if it uses the external fftw library, it can only use the fftwf
variant, i.e the fftw-single variant. Otherwise, it uses its internal
FFT library.
There is no way for liquid-dsp to use fftw-double or fftw-long-double.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Signed-off-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
When one of BR2_PACKAGE_FFTW_PRECISION_* is enabled, liquid-dsp links
against fftw3f, fftw3 or fftw3l, but forgets to add the fftw package
in its dependencies. It works fine in practice because "fftw" is
before "liquid-dsp" in the alphabetic ordering, but building with
"make liquid-dsp" or with per-package directory causes a build
failure.
Fix that by adding the missing dependencies.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Tested-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>
Reviewed-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
When a powerpc target is detected the build system tries to force
altivec support but that's wrong:
Not every powerpc processor has altivec instruction support.
It's using the removed/deprecated -faltivec compiler directive when it
should be using -maltivec instead.
Even if the above conditions are corrected the altivec codepath fails
to build properly.
So just disable altivec in general using the standard
--enable-simdoverride configure option. Fixes:
http://autobuild.buildroot.net/results/e1b/e1b6cf76a7a4ae754a928d211e779e9381198f48/
Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
By default, the liquid-dsp configure script looks at the current CPU
to find which x86 CPU extensions are supported. Those checks use
AC_TRY_RUN(), which cannot work in a cross-compilation environment,
and would anyway be wrong.
To fix this, we explicitly pass the appropriate ac_cv_have_<foo>_ext
autoconf cache variables.
Fixes:
http://autobuild.buildroot.org/results/eb0/eb002463ed82de461fae11211415c07883a95386/
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
[Thomas:
- add patch to fix autoreconf issue, and use LIQUID_DSP_AUTORECONF =
YES instead of an horrible hack calling aclocal/autoconf manually.
- use the github macro instead of hand-coding <pkg>_SITE and
<pkg>_SITE_METHOD. This allows to remove <pkg>_SITE_METHOD
entirely.
- use a full hash as the <pkg>_VERSION
- remove trailing whitespace everywhere.
- use one single assignment of LIQUID_DSP_CONF_OPTS
- fix the comment about the eglibc/musl dependency (it was only
mentioning eglibc, and the condition was inverted)
- add the musl/glibc dependency on the package option itself
- make the package depend on dynamic library support, since the
makefile unconditionally builds a shared library.
- add hash file.]
Signed-off-by: Guillaume William Bres <guillaume.bressaix@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Bernd Kuhls