Luca Ceresoli [Wed, 1 Oct 2014 15:03:45 +0000 (17:03 +0200)]
freescale/imx6-sabresd: lock down kernel headers to the kernel version
The current defconfigs for iMX6 SABRESD kernel 3.10.17 from the Freescale
git repository. This kernel is older than the toolchain kernel headers
used in Buildroot (currently 3.16.3).
Explicitly lock down the kernel headers to match the version of the kernel
that is built.
The stable-1.1 branch of freerdp fails to build when using a uClibc
toolchain because it's using functions which are not implemented in
uClibc, like eventfd_read, eventfd_write and futimes. That is causing
build failures like these ones:
../../libwinpr/synch/libwinpr-synch.so.0.1.0: undefined reference to
`eventfd_read'
../../libwinpr/synch/libwinpr-synch.so.0.1.0: undefined reference to
`eventfd_write'
../../common/libfreerdp-client.so.1.1.0: undefined reference to
`futimes'
Backport upstream patch, with non-applicable parts (new files from
master, but not in the stable-1.1 branch) trimmed down.
Fixes CVE-2014-3634 - potential abort when a message with PRI > 191 was
processed if the "pri-text" property was used in active templates, this
could be abused to a remote denial of service from permitted senders.
Fixes:
CVE-2014-6051 and
CVE-2014-6052 denial of service and possible code execution via
integer overflow and lack of malloc error handling in
MallocFrameBuffer()
CVE-2014-6053 denial of service via large ClientCutText message.
CVE-2014-6054 denial of service via zero scaling factor.
CVE-2014-6055 denial of service and possible code execution via
stack overflows in File Transfer feature.
Currently, the MESSAGE macro double-quotes the message. But a few call
sites also double-quote the message, resulting in a borked call to echo,
like:
$(call MESSAGE,"user text")
would expand to:
echo "Leading text "user message" trailign text"
Just use qstrip on the user message, so we get protected from either a
comma in the user text (so make does not interpret it), or a semi-colon
(so the shell does not interpret it.)
- Bump version to 1.5.9
- Remove patches already included in this version
- Use make parameters instead of environment variables
- Add an upstream patch to fix building statically
- Adapt old patches to the new version
- Add a hash file
The Makefile of dosfstools passes -D_GNU_SOURCE to get access to
non-standard definitions such as 'loff_t'. But this flag gets dropped
by the CFLAGS override, so explicitly add it.
When libcurl-0001-build-link-curl-to-NSS-libraries-when-NSS-support.patch
was removed the corresponding autoreconf was left behind:
http://git.buildroot.net/buildroot/commit/?id=9185b64ed5599622cb89ca4ee6ee29440b02ec8a
package/mtd: install libubi.a and libmtd.a to staging
Currently, the mtd package only installs the mtd utilities into the
target directory. However, the mtd-utils also provide two
static libraries (libmtd.a and libubi.a) that can be used by other
packages or tools.
Therefore, this commit extends the mtd package by adding the
installation to the staging directory of those two libraries.
The VideoCore file server daemon startup script installed from this package is
not compatible with BuildRoot (because of its naming and other Debian
dependencies), which prevented vcfiled from starting. Hence, prevent this
package from installing its vcfiled startup script, and add a configuration
option to install a vcfiled SysV init script suitable for BuildRoot.
Samuel Martin [Thu, 21 Aug 2014 20:45:20 +0000 (22:45 +0200)]
toolchainfile.cmake.in: do not force the CMAKE_{C, CXX}_FLAGS to the cache
Fix #7280 [1]
When the FORCE option is passed to the set command, the variable is
added/updated in the CMake cache every single time CMake processes this
command.
Because the toolchainfile.cmake prepends architecture/toolchain flags
to the CMAKE_{C,CXX}_FLAGS, this makes the CFLAGS being updated in the
generated Makefiles each time one reconfigures its project. So it
forces the compilation of everything, even when nothing has changed.
[1] https://bugs.busybox.net/show_bug.cgi?id=7280
Signed-off-by: Samuel Martin <[email protected]> Tested-by: Thomas De Schampheleire <[email protected]>
(tested the SimpleApp reproduction scenario described in the bug report) Signed-off-by: Peter Korsgaard <[email protected]>
jamvm: bump to 2.0.0 (including mips big-endian support)
This commit bumps jamvm to version 2.0.0. From the release notes:
I'm pleased to announce a new release of JamVM. JamVM 2.0.0 is the
first release of JamVM with support for OpenJDK (in addition to GNU
Classpath). Although IcedTea already includes JamVM with OpenJDK
support, this has been based on periodic snapshots of the development
tree.
JamVM 2.0.0 supports OpenJDK 6, 7 and 8 (the latest). With OpenJDK 7 and
8 this includes full support for JSR 292 (invokedynamic). JamVM 2.0.0
with OpenJDK 8 also includes full support for Lambda expressions (JSR
335), type annotations (JSR 308) and method parameter reflection.
In addition to OpenJDK support, JamVM 2.0.0 also includes many
bug-fixes, performance improvements and improved compatibility (from
running the OpenJDK jtreg tests).
As this release now also supports MIPS big-endian targets, this commit
fixes bug #7010 (https://bugs.busybox.net/show_bug.cgi?id=7010)
Not all cdrkit variables are prefixed with CDRKIT_, so they leak.
Most importantly, they look like they belong to another package's
namespace, cmake, as they start with CMAKE_ (but fortunately, they
have no impact on cmake, as they are not used by our infras.)
Fix that by removing the intermediate variables, and directly set
the CDRKIT_CONF_OPT variable.
OpenCV's highgui module needs to be auto-selected when the ts module is
selected, because it depends on it. Otherwise it would fail with an
error like this one:
[ 96%] Building CXX object
modules/ts/CMakeFiles/opencv_ts.dir/src/gpu_perf.cpp.o
In file included from
/home/test/autobuild/instance-1/output/build/opencv-2.4.8/modules/ts/src/gpu_perf.cpp:43:0:
/home/test/autobuild/instance-1/output/build/opencv-2.4.8/modules/ts/include/opencv2/ts/gpu_perf.hpp:47:39:
fatal error: opencv2/highgui/highgui.hpp: No such file or directory
compilation terminated.
The gnuplot 4.6.6 tarball was updated because of this:
(based on a diff from the original release and the updated one)
http://thread.gmane.org/gmane.comp.graphics.gnuplot.user/7856
Some packages use -lcurses when they are linking, so they try to link to
a library called libcurses. The library provided by our ncurses package
is called libncurses, so those packages fail to link with a message like
this one:
/bin/ld: cannot find -lcurses
Installing a libcurses symlink to libncurses fixes the problem.
Also update our 6x_upgrade script to the version from that page so the
entire SPI flash gets erased (otherwise it fails on big u-boot builds) and
document how to perform the upgrade.
This commit adds a new patch to the ARC 2014.08 gcc specific version,
that redefines PTRDIFF_TYPE from "long int" to "int".
The change of SIZE_TYPE from "long unsigned int" to "unsigned int"
http://git.buildroot.net/buildroot/commit/?id=0f236c1fef669192c8f5cc8ef26e93da91438dc2
introduced a regression due to the existing PTRDIFF_TYPE.
Now to fix regression the patch converts PTRDIFF_TYPE to simple "int".
The fix is taken from current development branch of GCC for ARC and
will be a part of the next release of ARC tools, so at that point
patch should be dropped.
Peter Seiderer [Mon, 22 Sep 2014 20:54:50 +0000 (22:54 +0200)]
util-linux: disable more command for host build
Fixes the following compile error (in case neither curses or ncurses
development files are installed on the build host):
text-utils/more.c: In function ‘screen’:
text-utils/more.c:692:4: warning: implicit declaration of function ‘my_putstring’ [-Wimplicit-function-declaration]
text-utils/more.c:692:4: warning: nested extern declaration of ‘my_putstring’ [-Wnested-externs]
text-utils/more.c: In function ‘initterm’:
text-utils/more.c:1798:3: warning: implicit declaration of function ‘my_setupterm’ [-Wimplicit-function-declaration]
text-utils/more.c:1798:3: warning: nested extern declaration of ‘my_setupterm’ [-Wnested-externs]
text-utils/more.c:1806:5: warning: implicit declaration of function ‘my_tgetnum’ [-Wimplicit-function-declaration]
text-utils/more.c:1806:5: warning: nested extern declaration of ‘my_tgetnum’ [-Wnested-externs]
text-utils/more.c:1806:22: error: ‘TERM_LINES’ undeclared (first use in this function)
text-utils/more.c:1806:22: note: each undeclared identifier is reported only once for each function it appears in
text-utils/more.c:1807:23: error: ‘TERM_COLS’ undeclared (first use in this function)
text-utils/more.c:1816:4: warning: implicit declaration of function ‘my_tgetflag’ [-Wimplicit-function-declaration]
text-utils/more.c:1816:4: warning: nested extern declaration of ‘my_tgetflag’ [-Wnested-externs]
text-utils/more.c:1816:34: error: ‘TERM_HARD_COPY’ undeclared (first use in this function)
text-utils/more.c:1821:20: error: ‘TERM_EAT_NEW_LINE’ undeclared (first use in this function)
text-utils/more.c:1827:23: error: ‘TERM_AUTO_RIGHT_MARGIN’ undeclared (first use in this function)
text-utils/more.c:1828:25: error: ‘TERM_CEOL’ undeclared (first use in this function)
text-utils/more.c:1829:4: warning: implicit declaration of function ‘my_tgetstr’ [-Wimplicit-function-declaration]
text-utils/more.c:1829:4: warning: nested extern declaration of ‘my_tgetstr’ [-Wnested-externs]
text-utils/more.c:1829:25: error: ‘TERM_CLEAR_TO_LINE_END’ undeclared (first use in this function)
text-utils/more.c:1830:23: error: ‘TERM_CLEAR’ undeclared (first use in this function)
text-utils/more.c:1831:24: error: ‘TERM_STANDARD_MODE’ undeclared (first use in this function)
text-utils/more.c:1832:23: error: ‘TERM_EXIT_STANDARD_MODE’ undeclared (first use in this function)
text-utils/more.c:1833:31: error: ‘TERM_STD_MODE_GLITCH’ undeclared (first use in this function)
text-utils/more.c:1842:20: error: ‘TERM_UNDERLINE’ undeclared (first use in this function)
text-utils/more.c:1843:23: error: ‘TERM_OVER_STRIKE’ undeclared (first use in this function)
text-utils/more.c:1845:27: error: ‘TERM_UNDERLINE_CHAR’ undeclared (first use in this function)
text-utils/more.c:1848:21: error: ‘TERM_ENTER_UNDERLINE’ undeclared (first use in this function)
text-utils/more.c:1850:17: error: ‘TERM_EXIT_UNDERLINE’ undeclared (first use in this function)
text-utils/more.c:1862:29: error: ‘TERM_PAD_CHAR’ undeclared (first use in this function)
text-utils/more.c:1864:22: error: ‘TERM_HOME’ undeclared (first use in this function)
text-utils/more.c:1867:21: error: ‘TERM_CURSOR_ADDRESS’ undeclared (first use in this function)
text-utils/more.c:1869:10: warning: implicit declaration of function ‘my_tgoto’ [-Wimplicit-function-declaration]
text-utils/more.c:1869:10: warning: nested extern declaration of ‘my_tgoto’ [-Wnested-externs]
text-utils/more.c:1869:10: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
text-utils/more.c:1876:24: error: ‘TERM_CLEAR_TO_SCREEN_END’ undeclared (first use in this function)
text-utils/more.c:1877:27: error: ‘TERM_LINE_DOWN’ undeclared (first use in this function)
text-utils/more.c: In function ‘reset_tty’:
text-utils/more.c:2142:3: warning: implicit declaration of function ‘tputs’ [-Wimplicit-function-declaration]
text-utils/more.c:2142:3: warning: nested extern declaration of ‘tputs’ [-Wnested-externs]
make[4]: *** [text-utils/more-more.o] Error 1
Max Filippov [Tue, 23 Sep 2014 03:23:29 +0000 (07:23 +0400)]
binutils: fix 'call8: call target out of range' xtensa ld bug
This fixes the following linux kernel build errors:
LD init/built-in.o
net/built-in.o: In function `raw_proc_exit':
(.init.text+0xe29): dangerous relocation:
call8: call target out of range: udp_proc_register
net/built-in.o: In function `udp_table_init':
(.init.text+0xf09): dangerous relocation:
call8: call target out of range: udp_proc_register
net/built-in.o: In function `inet_init':
af_inet.c:(.init.text+0x142e): dangerous relocation:
call8: call target out of range: udp4_proc_exit
net/built-in.o: In function `ip_auto_config':
ipconfig.c:(.init.text+0x28aa): dangerous relocation:
call8: call target out of range: arp_send
directfb-fusion uses the madvise() system call which is not available
on no-MMU targets.
It seems it might be possible to simply remove the call to madvise()
(there is only one call) if not available. However, it's probably not
worth the effort, and people working on no-MMU targets can submit a
patch doing that if they are interested.
Version 1.0.0 was not compatible with systemd. With 1.0.0, systemd
compilation produce:
src/shared/seccomp-util.c: In function 'seccomp_add_secondary_archs':
src/shared/seccomp-util.c:73:9: warning: implicit declaration of function 'seccomp_arch_add' [-Wimplicit-function-declaration]
r = seccomp_arch_add(c, SCMP_ARCH_X86);
^
src/shared/seccomp-util.c:73:9: warning: nested extern declaration of 'seccomp_arch_add' [-Wnested-externs]
src/shared/seccomp-util.c:73:33: error: 'SCMP_ARCH_X86' undeclared (first use in this function)
r = seccomp_arch_add(c, SCMP_ARCH_X86);
^
src/shared/seccomp-util.c:77:33: error: 'SCMP_ARCH_X86_64' undeclared (first use in this function)
r = seccomp_arch_add(c, SCMP_ARCH_X86_64);
^
src/shared/seccomp-util.c:81:33: error: 'SCMP_ARCH_X32' undeclared (first use in this function)
r = seccomp_arch_add(c, SCMP_ARCH_X32);
Jeremy Rosen [Mon, 22 Sep 2014 11:31:08 +0000 (13:31 +0200)]
swig: add swig2.0 -> swig symlink
The cmake detection script provided with cmake will first look for a
binary called swig2.0 then for a binary called swig.
host-swig only installs a binary called swig, but if the host
distribution has instaled a binary called swig2.0, it will be
preferred over our swig, which isn't great. This patch creates a
symlink swig2.0 -> swig to prevent this from happening.
[Thomas: add comment in the code and improve the commit log]
Jeremy Rosen [Mon, 22 Sep 2014 11:31:07 +0000 (13:31 +0200)]
cmake : bump to version 3.0.2
The
cmake-0001-FindQt4-do-not-prepend-CMake-root-path-when-searchin.patch
patch has been merged upstream as part of commit e8b8b37ef6fef094940d3384df5a1d421b9fa568.
[Thomas: tweak commit log by adding details about the patch being
removed.]
projects / buildroot-mgba.git / log