Matt Weber [Thu, 21 Jan 2016 03:31:47 +0000 (03:31 +0000)]
iputils: resolve musl compatibility
The new upstream is a fork of the original that consolidates other distro's
patches. This fork resolves a series of musl build failures noted in the
autobuilder log.
- Updated to github fork, selected merge from Nov 3 2015
which provided musl fixes (last release was to old, 20150815)
- Why the fork ? (http://www.spinics.net/lists/netdev/msg279881.html)
- Added missing dependencies for kernel capabilies lib
- Accounted for new consolidated ping (ipv4/6)
Tested against a buildroot arm musl/glibc toolchains, as well as
autobuilder defconfig.
Signed-off-by: Matt Weber <matt@thewebers.ws> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Thomas Petazzoni [Thu, 21 Jan 2016 14:25:55 +0000 (15:25 +0100)]
libv4l: update upstream status of patches
After some effort to upstream the libv4l patches, 4 out of our 5
patches are now upstream. This commit updates those patches to
indicate their upstream status.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Thomas Petazzoni [Thu, 21 Jan 2016 09:52:02 +0000 (10:52 +0100)]
libv4l: add patch to fix libjpeg build issue
Since the bump of libjpeg to v9b, libv4l doesn't build anymore due to
the change of the prototype of jpeg_mem_src(), which gets
re-implemented in libv4l when the libjpeg is too old.
Julien Floret [Tue, 19 Jan 2016 11:10:53 +0000 (12:10 +0100)]
lldpd: new package
lldpd is a 802.1ab implementation (LLDP) to help you locate neighbors
of all your equipments.
LLDP is an industry standard protocol designed to supplant proprietary
Link-Layer protocols such as EDP or CDP. The goal of LLDP is to
provide an inter-vendor compatible mechanism to deliver Link-Layer
notifications to adjacent network devices.
https://vincentbernat.github.io/lldpd/
[Thomas:
- add depends on BR2_USE_MMU, since fork() is used
- rewrap Config.in help text]
Signed-off-by: Julien Floret <julien.floret@6wind.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Lada Trimasova [Wed, 20 Jan 2016 15:21:18 +0000 (18:21 +0300)]
alsa-lib: disable libdl for static only builds
-ldl includes the reference to the library that has
the symbols for loading dynamic libraries.
So there is no need for this library for static only builds.
Even though alsa-lib uses dlopen, it has functions snd_dlopen
and others which can emulate dynamic linking for the static
build of the alsa-lib library and there is no need in libdl
dlopen when static build only.
This patch fixes build failures of the shairport-sync
(and probably other packages) when static libs are used.
skeleton: move LIB_SYMLINK definition from Makefile
Commit 7a6b83a211612ff95a1f5d35b2861ad5655ac8b1 introduced the skeleton
package, which took over the lib32/lib64 -> lib symlink creation from the
main Makefile.
However, the definition of the LIB_SYMLINK variable did not move along, for
no real reason.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Arnout Vandecappelle <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Lada Trimasova [Wed, 20 Jan 2016 18:42:31 +0000 (21:42 +0300)]
gcc: immediate changes to arc-2015.12-rc1
These patches solve several problems that were discovered
after bumping tools to arc-2015.12-rc1.
The fixes were done in development tree arc-4.8-dev and will be
a part of the next release of ARC GNU tools.
Once that new release happens these patches must be removed.
Signed-off-by: Lada Trimasova <ltrimas@synopsys.com> Cc: Alexey Brodkin <abrodkin@synopsys.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Gustavo Zacarias [Wed, 20 Jan 2016 16:53:40 +0000 (13:53 -0300)]
libungif: remove deprecated
It's been deprecated for a year now, so remove it.
While at it also remove the BR2_DEPRECATED_SINCE_2015_02 since it's now
unused.
And change the efl gif text to refer to giflib rather than libungif
which is what's used since it was deprecated.
Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
libnspr currently passes --enable-thumb2 if the CPU has thumb
instructions. This option will pass -mthumb to the compiler. However,
if an external multilib toolchain is used that has a thumb-specific
variant (e.g. Sourcery), it will try to use that one. But we only copy
a single variant to the sysroot, so the build will fail with:
.../arm-none-linux-gnueabi/bin/ld: cannot find crti.o: No such file or directory
...
collect2: error: ld returned 1 exit status
../../config/rules.mk:303: recipe for target 'libnspr4.so' failed
We can in fact just remove the thumb2 handling. With current libnspr,
the thumb and thumb2 options just add -marm and -mthumb. But we already
pass that in our toolchain wrapper so it's completely redundant.
Note that when nothing is passed, the configure script still tries to
autodetect whether thumb2 is available (but doesn't do it correctly,
see the error above), but in the end it doesn't use the result for
anything. In other words, even if it detects that thumb2 is available,
it will _not_ pass -mthumb to the compiler.
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Yann E. MORIN [Mon, 9 Nov 2015 19:00:21 +0000 (20:00 +0100)]
core: fix setting of HOSTARCH
Currently, we set HOSTARCH to the output of `uname -m`. This gives us
the architecture as seen by the running kernel. For example, we would
end up with 'x86_64' for a 64-bit kernel running on an x86_64 processor.
We use that value to determine whether we can run some binary tools,
like our pre-configured external toolchains.
However, one may be running a userland in a different bitness than that
of the running kernel. For example, one may run in a 32-bit chroot, even
though the kernel is running in 64-bit.
Up until recently, this was not an issue because the pre-configured
external toolchains were all requiring an i386 (x86 in Buildroot
parlance).
But since we introduced the latest Linaro toolchains, we now have
toolchains that require a 64-bit userland.
So, when running on a 64-bit kernel, we believe those toolchains are
available, even when the user is running a 32-bit userland. This causes
build failures for our autobuilders, like so:
Besides fixing those issues, it will also allow us to add the 64-bit
variants of toolchains when they exist, like the upcoming Codescape
MTI and IMG toolchains for MIPS from Imagination Technologies.
[Peter: use HOSTCC_NOCCACHE] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Currently our toolchain infrastructure assumes that every toolchain has
nested sysroot directories. However that's not true for all of them. The
Codescape toolchains from Imagination Technologies use a side by side
sysroot structure, for instance.
This patch allows our toolchain infrastructure to detect what kind of
sysroot structure we have (nested or side by side) and performs the
appropriate actions.
[Thomas: update the comment above the function, to explain what's
going on with nested sysroots and side-by-side sysroots.]
Jörg Krause [Tue, 19 Jan 2016 09:51:53 +0000 (10:51 +0100)]
package/triggerhappy: bump to latest commit to fix runtime issue
Bump to latest commit to fix runtime issue with the Linux Kernel headers 4.4:
Starting thd: Unable to parse trigger line: [..]
With version 4.4 of the Linux Kernel the input event codes are not defined in
'linux/input.h' anymore, but in a seperate header file
'linux/input-event-codes.h' leaving triggerhappys evtable_*.h header files
empty with no event codes defined.
Yann E. MORIN [Sat, 16 Jan 2016 22:37:21 +0000 (23:37 +0100)]
docs/manual: add ordering of kconfig options' attributes
We want to ensure all packages follow the same coding style, so we add a
blurb about the order of kconfig options' attributes:
- first, the type and the prompt
- the default value if needed
- then dependencies of the 'depends on' category
- followed by dependencies of the 'select' form
- with eventually the help text
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Yann E. MORIN [Sat, 16 Jan 2016 22:36:54 +0000 (23:36 +0100)]
package/alsa-utils: use 'menuconfig' instead of 'config'+'menu'
Drop the now useless comment.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Alexey Brodkin [Mon, 18 Jan 2016 10:17:31 +0000 (13:17 +0300)]
toolchain: bump ARC toolchain components to arc-2015.12-rc1
This change introduces newer ARC toolchain in Buildroot.
Note this is the first release candidate and we'll probably see another
RC before cutting the final release.
That new arc-2015.12 release doesn't bring any significant changes but
mostly is focused on fixes and minor improvements here and there.
Most noticeable changes are:
* GCC updated to v4.8.5
* GDB updated to 7.10
You may find more info on fixes and improvements in that release at:
https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases/tag/arc-2015.12-rc1
Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: arc-buildroot@synopsys.com Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Otherwise it will cause build failures like this one:
[100%] Linking C executable luvi
/home/buildroot/autobuild/run/instance-2/output/host/opt/ext-toolchain/bin/../lib/gcc/mipsel-buildroot-linux-gnu/5.2.0/../../../../mipsel-buildroot-linux-gnu/bin/ld:
jitted_tmp/src/lua/init.lua_luvi_generated.o: compiled for a big endian
system and target is little endian
Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Hollis Blanchard [Wed, 12 Aug 2015 00:11:49 +0000 (17:11 -0700)]
linux: handle read-only dts files
Some fine version control systems make all files read-only. The custom DTS file
may therefore be read-only, and that permission is preserved when copying into
the Linux build directory. A subsequent rebuild tries to 'cp' again, which
fails with a "Permission denied" error unless the -f option is used.
Signed-off-by: Hollis Blanchard <hollis_blanchard@mentor.com> Acked-by: Nikolay Dimitrov <picmaster@mail.bg> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Thomas Petazzoni [Tue, 19 Jan 2016 20:45:48 +0000 (21:45 +0100)]
python-pydal: remove useless empty newline
There is an empty newline between the "help" keyword, and the help
text, which we don't normally do in Buildroot. This commit gets rid of
this useless empty newline.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
libffi: fix the build for MIPS soft-float with recent compilers
Recent MIPS compilers have an stricter agreement between the compiler
and the assembler on the ABI. The compiler now passes -msoft-float to
the assembler where it previously did not.
libffi uses MIPS hard-float instructions so when we try to build it for
soft-float using a recent compiler it fails because of the explained
above. This package should be fixed in order to add support for
soft-float.
In the meantime we can add a little hack in order to be able to build it
for soft-float. Basically we add ".set hardfloat" so the assembler will
not disable the hard-float instructions. The build will of course
include some hard-float bits which shouldn't exist in a soft-float
build, and that may cause runtime problems. But that's what we already
had before and we had lived with it.
We choose to apply this temporary fix because it only affects MIPS
soft-float builds. Otherwise we would need to disable libffi and
recursively all the packages depending on it (python, libglib2...) for
MIPS soft-float, which would be a bit overkill.
Vincent Dehors [Fri, 8 Jan 2016 14:32:19 +0000 (15:32 +0100)]
gst1-plugins-ugly: Add option for building x264 plugin
As x264 is packaged, we can also build the gstreamer plugin using it.
This commit adds the option in menuconfig and make sure it is built if
selected.
[Peter: split fix, add GPL tag, update help text and commit description] Signed-off-by: Vincent Dehors <vincent.dehors@openwide.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Thomas Petazzoni [Mon, 18 Jan 2016 21:01:09 +0000 (22:01 +0100)]
gst1-plugins-bad: add kernel header version dependency on DVB plugin
The DVB plugin uses the FEC_2_5 and QAM_4_NR from the DVB API, which
were added only in kernel 3.7. This commit adds the necessary kernel
header version dependency, which fixes:
Yann E. MORIN [Sun, 17 Jan 2016 14:26:09 +0000 (15:26 +0100)]
support/download: support older bazaar versions
In efe7f68 (support/download: generate reproducible Bazaar archives),
bzr was instructed to store files with the timestamp set to the date
they were last modified in the repository, instead of the current date,
using the --per-file-timestamp option.
However, this option has been added only in bzr-2.2 (August 2010) which
is not available on older distros.
We fix that by not using --per-file-timestamp when the bzr version is
older than 2.2, in which case we just generate the archive with the
current date set on files.
This means the archive is thus non-reproducible, and if a hash is
available for that archive, the hash will not match, and Buildroot will
try to download from the mirror (if any) or fail (if no mirror).
[Peter: simplify sed invocation] Reported-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Thomas Petazzoni [Sat, 16 Jan 2016 17:12:22 +0000 (18:12 +0100)]
bluez5_utils: not available with uClibc
Since the bump from 5.27 to 5.37 of bluez5_utils, the bluez code has
started using <wordexp.h> functionality. Unfortunately, our current
uClibc configuration does not have the wordexp functionality enabled,
so bluez5_utils cannot be built anymore.
In order to address this, we make bluez5_utils unavailable on
uClibc. This could be changed later by either removing the dependency
of bluez5_utils on wordexp support, or by deciding to add wordexp
support to our uClibc configuration.
Thomas Petazzoni [Sat, 16 Jan 2016 16:57:07 +0000 (17:57 +0100)]
alsa-utils: put 'select' after 'bool'
In the definitions of the alsa-utils sub-options, the 'select' were
before the 'bool', which is unusual and does not follow how we do
things in general in Buildroot. This commit fixes that for all
alsa-utils suboptions.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Thomas Petazzoni [Sat, 16 Jan 2016 16:55:03 +0000 (17:55 +0100)]
alsa-utils: needs dynamic library support
Since recent bumps of alsa-lib and alsa-utils, alsa-lib installs
<alsa/topology.h>, which alsa-utils uses to build an alsatplg program
which requires <dlfcn.h>. Therefore, alsa-utils now needs dynamic
library support.
Peter Seiderer [Thu, 14 Jan 2016 21:44:21 +0000 (22:44 +0100)]
assimp: fix compile for big endian target
Patch taken from upstream [1].
Fixes ([2]):
code/Bitmap.cpp: In function 'std::size_t Assimp::Copy(uint8_t*, T&) [with T = short unsigned int, std::size_t = unsigned int, uint8_t = unsigned char]':
code/Bitmap.cpp:95:50: instantiated from here
code/Bitmap.cpp:87:9: error: lvalue required as unary '&' operand
Peter Seiderer [Thu, 14 Jan 2016 21:44:20 +0000 (22:44 +0100)]
assimp: fix bfin compile
Use proper 64-bit constant for CONVERT_FBX_TIME(time) conversion.
Fixes ([1]):
code/FBXConverter.cpp:2025: error: integer constant is too large for 'long' type
code/FBXConverter.cpp:2026: error: integer constant is too large for 'long' type
code/FBXConverter.cpp:2794: error: integer constant is too large for 'long' type
code/FBXConverter.cpp:2868: error: integer constant is too large for 'long' type
code/FBXConverter.cpp:2878: error: integer constant is too large for 'long' type
code/FBXConverter.cpp:2888: error: integer constant is too large for 'long' type
The perf tool installed test files in
output/target/usr/libexec/perf-core/tests/
which amounted to about 30+K.
Since they are not needed for normal perf operation, remove them.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Joris Lijssens [Fri, 15 Jan 2016 15:03:40 +0000 (16:03 +0100)]
netsniff-ng: check if linux-headers are v3.0 or higher
netsniff-ng uses the TP_STATUS_VLAN_VALID define, provided by the
kernel headers. This definition has been added in the kernel by commit a3bcc23e890a6d49d6763d9eb073d711de2e0469 ("af-packet: Add flag to
distinguish VID 0 from no-vlan"), which was merged in v3.0.
projects / coffee / buildroot.git / log