buildroot/package/uclibc, branch 2019.02-op-build

package/uclibc: add custom bits/poll.h for xtensa

2018-12-13T20:19:06+00:00

Definitions of POLLWRNORM, POLLWRBAND and POLLREMOVE in xtensa linux kernel are non-standard. Provide bits/poll.h with correct values for these constants for uclibc-ng. This fixes the following strace build errors: In file included from xlat/pollflags.h:4:0, from poll.c:34: ./static_assert.h:40:24: error: static assertion failed: "POLLWRBAND != 0x0100" # define static_assert _Static_assert ^ xlat/pollflags.h:75:1: note: in expansion of macro ‘static_assert’ static_assert((POLLWRBAND) == (0x0100), "POLLWRBAND != 0x0100"); ^~~~~~~~~~~~~ ./static_assert.h:40:24: error: static assertion failed: "POLLREMOVE != 0x0800" # define static_assert _Static_assert ^ xlat/pollflags.h:117:1: note: in expansion of macro ‘static_assert’ static_assert((POLLREMOVE) == (0x0800), "POLLREMOVE != 0x0800"); ^~~~~~~~~~~~~ Fixes: http://autobuild.buildroot.net/results/5a0112b7a2c81fa5253c9adc93efe415256cd811 Signed-off-by: Max Filippov Reviewed-by: Baruch Siach Signed-off-by: Thomas Petazzoni

package/uclibc: add upstream patch to fix aarch64 issues

2018-12-03T08:15:21+00:00

fstatfs/statfs on aarch64 seems broken, add a patch from uClibc-ng upstream git to fix it. Signed-off-by: Waldemar Brodkorb Signed-off-by: Thomas Petazzoni

Merge branch 'next'

2018-12-02T07:16:10+00:00

Signed-off-by: Peter Korsgaard

package/uclibc: bump to version 1.0.31

2018-11-25T08:14:14+00:00

Remove all patches, since they were already applied upstream. Add license file hash. Signed-off-by: Carlos Santos Signed-off-by: Thomas Petazzoni

uclibc: Get rid of stale UCLIBC_INSTALL_LDSO_SYMLINKS

2018-11-18T19:18:08+00:00

UCLIBC_INSTALL_LDSO_SYMLINKS is not defined anywhere to nuke it. Signed-off-by: Alexey Brodkin Acked-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

toolchain: disable SSP support if CFI support in binutils is missing

2018-11-04T11:49:25+00:00

As reported by [1], SSP support is missing in the Buildroot toolchain for microblaze even if it's requested by selecting BR2_TOOLCHAIN_HAS_SSP config option. In Buildroot, we are using libssp provided by the C library (glibc, musl, uClibc-ng) when available. We are not using libssp from gcc. So for a microblaze glibc based toolchain, the SSP support is enabled unconditionally by a select BR2_TOOLCHAIN_HAS_SSP. BR2_microblazeel=y BR2_TOOLCHAIN_BUILDROOT_GLIBC=y BR2_KERNEL_HEADERS_4_14=y BR2_BINUTILS_VERSION_2_30_X=y BR2_GCC_VERSION_8_X=y BR2_TOOLCHAIN_BUILDROOT_CXX=y While building the toolchain, we are building host-binutils which provide "as" (assembler) and host-gcc-initial wich provide a minimal cross gcc (C only cross-compiler without any C library). When SSP support is requested, gcc_cv_libc_provides_ssp=yes is added to the make command line (see [2] for full details) With this setting, the SSP support is requested but it's not available in the end and the toochain build succeed. When the microblaze toolchain is imported to Biuldroot (2018.05) as external toolchain with BR2_TOOLCHAIN_EXTERNAL_HAS_SSP set, the build stop with : "SSP support not available in this toolchain, please disable BR2_TOOLCHAIN_EXTERNAL_HAS_SSP" The test is doing the following command line: echo 'void main(){}' | [...]/host/bin/microblazeel-linux-gcc.br_real -Werror -fstack-protector -x c - -o [...]/build/.br-toolchain-test.tmp cc1: error: -fstack-protector not supported for this target [-Werror] When we look at the gcc-final log file (config.log) we can see this error several time when using the minimal gcc (from host-gcc-initial). So Why the minimal gcc doesn't support SSP? When we look at the gcc-initial log file (config.log) we can see an error with 'as': configure:23194: checking assembler for cfi directives configure:23209: [...]microblazeel-buildroot-linux-gnu/bin/as -o conftest.o conftest.s >&5 conftest.s: Assembler messages: conftest.s:2: Error: CFI is not supported for this target conftest.s:3: Error: CFI is not supported for this target conftest.s:4: Error: CFI is not supported for this target conftest.s:5: Error: CFI is not supported for this target conftest.s:6: Error: CFI is not supported for this target conftest.s:7: Error: CFI is not supported for this target configure:23212: $? = 1 configure: failed program was .text .cfi_startproc .cfi_offset 0, 0 .cfi_same_value 1 .cfi_def_cfa 1, 2 .cfi_escape 1, 2, 3, 4, 5 .cfi_endproc This is the only relevant difference compared to a nios2 toolchain where libssp is enabled and available (nios2 is an example). "CFI" stand for "Control Flow Integrity" and it seems that SSP support requires CFI target support (see [3] for some explanation). The SSP support seems to depends on CFI support, but the toolchain infrastructure is not detailed enough to handle the CFI dependency. The NiosII toolchains built with binutils < 2.30 are also affected by this issue. This patch improve the toolchain infrastructure by adding a new BR2_PACKAGE_HOST_BINUTILS_SUPPORTS_CFI blind option Disable SSP support for microblaze entirely. Disable SSP support for nios2 only with Binutils < 2.30. Fixes: https://gitlab.com/free-electrons/toolchains-builder/-/jobs/72006389 [1] https://gitlab.com/free-electrons/toolchains-builder/issues/1 [2] https://git.buildroot.net/buildroot/tree/package/gcc/gcc.mk?h=2018.05#n275 [3] https://grsecurity.net/rap_faq.php Signed-off-by: Romain Naour Cc: Thomas Petazzoni [Thomas: adjust how the BR2_PACKAGE_HOST_BINUTILS_SUPPORTS_CFI option is expressed.] Signed-off-by: Thomas Petazzoni

uclibc: fix mkostemp

2018-10-31T11:45:21+00:00

Pull a patch already submitted upstream[1] that fixes mkostemp when _LARGEFILE64_SOURCE is defined. This is required to prevent failures on eudev[2]: # udevadm hwdb --update Failure writing database //etc/udev/hwdb.bin: Invalid argument 1. https://patchwork.ozlabs.org/patch/990045/ 2. https://patchwork.ozlabs.org/patch/984848/ Signed-off-by: Carlos Santos Signed-off-by: Peter Korsgaard

uclibc: ldso/arc: fix LD_DEBUG segv when printing R_ARC_NONE

2018-08-08T14:27:58+00:00

Dynamic linker used to segfault on attempt to print info about R_ARC_NONE reloaction. The fix is already in upstream master [1], should be removed on uClibc version bump. [1] https://cgit.uclibc-ng.org/cgi/cgit/uclibc-ng.git/commit/?id=269a2a2a0f863e1b43dc02f2f4f0f3c50299456e Signed-off-by: Alexey Brodkin Signed-off-by: Peter Korsgaard

arch: drop now useless support for FDPIC

2018-07-01T13:17:27+00:00

Now that we dropped support for blackfin, we no longer have any architecture that supports FDPIC, so BR2_ARCH_HAS_FDPIC_SUPPORT is never selected, so we can't select BR2_BINFMT_FDPIC. Drop all of that now. Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

uclibc: ARC: Don't mess with CPU selection

2018-05-19T20:47:22+00:00

Since uClibc-ng commit cde74b83f9b2 "ARC: remove special CFLAGS/LDFLAGS handling" i.e. starting v1.0.23 CONFIG_ARC_CPU_xx options are not used. Instead uClibc relies on toolchain defaults or build-system CFLAGS for selection of ARC-specific code (i.e. distinguishes between ARCompact and ARCv2 ISAs). So we drop corresponding quirks from Buildroot as well. Signed-off-by: Alexey Brodkin Cc: Thomas Petazzoni Cc: Waldemar Brodkorb Signed-off-by: Thomas Petazzoni