- Feb 01, 2016
-
-
Arnout Vandecappelle authored
In the hope of improving the quality of patches sent by newcomers, add a reference to the submitting-patches section of the manual to the top-level README file. Signed-off-by:
Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Romain Naour authored
In order to be abble to select BR2_ARM_FPU_VFPV3D16, BR2_ARM_ENABLE_VFP must be selected first. Signed-off-by:
Romain Naour <romain.naour@gmail.com> Signed-off-by:
-
Romain Naour authored
In order to be abble to select BR2_ARM_FPU_VFPV3D16, BR2_ARM_ENABLE_VFP must be selected first. Signed-off-by:
-
Peter Korsgaard authored
Commit dc95d50f (correct gettext handling for musl) introduced a last minute typo, fix that. Thanks to Thomas Petazzoni for noticing. Signed-off-by:
Peter Korsgaard <peter@korsgaard.com>
-
Peter Korsgaard authored
This reverts commit a0a244d2. As this is now handled globally in TARGET_CONFIGURE_ARGS, this can be reverted here. Signed-off-by:
-
Peter Korsgaard authored
Based on a patch by Bernd Kuhls. The AM_GNU_GETTEXT autotools macro misdetects musl gettext support as it checks for internal glibc symbols. Work around it by forcing libc gettext support when musl is used for the supported gettext api levels. As this is a generic issue for any package using AM_GNU_GETTEXT, add it to the global TARGET_CONFIGURE_ARGS instead of for each affected package. Signed-off-by: -
Jörg Krause authored
Signed-off-by:
Jörg Krause <joerg.krause@embedded.rocks> Signed-off-by:
-
Bernd Kuhls authored
Fixes http://autobuild.buildroot.net/results/020/020951a32ace3b4bca12a888eaaeb8b6c5633e4f/ [Peter: notice patch is now upstream: https://github.com/rpodgorny/unionfs-fuse/commit/f64b094eba93b042a1ed5964 ] Signed-off-by:
Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by:
-
Thomas De Schampheleire authored
Fix some typos and references to a size-stats 'target' (the script is called 'size-stats' but the make target is 'graph-size'). Signed-off-by:
Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Acked-by:
-
Bernd Kuhls authored
The build errors were not yet found by the autobuilders: action.c: In function ‘name_fn’: action.c:1911:29: error: ‘FNM_EXTMATCH’ undeclared (first use in this function) FNM_PATHNAME|FNM_PERIOD|FNM_EXTMATCH) == 0;) ^ pseudo.c: In function ‘read_pseudo_def’: pseudo.c:435:11: error: ‘S_IFBLK’ undeclared (first use in this function) mode |= S_IFBLK; ^ Signed-off-by: -
Thomas De Schampheleire authored
Currently, following symbolic links are created in both target and staging directories: - lib(32|64) --> lib - usr/lib(32|64) --> lib The decision for lib32 or lib64 is based on the target architecture configuration in buildroot (BR2_ARCH_IS_64). In at least one case this is not correct: when building for a Cavium Octeon III processor using the toolchain from the Cavium Networks SDK, and specifying -march=octeon3 in BR2_TARGET_OPTIMIZATION, libraries are expected in directory 'lib32-fp' rather than 'lib32' (ABI=n32; likewise for lib64-fp in case of ABI=n64) More generally the correct symbolic link is from (usr/)${ARCH_LIB_DIR}->lib. However, feedback from Arnout Vandecappelle is that there are packages that do depend on the lib32/lib64 symlink, even if ARCH_LIB_DIR is different. Hence, these links must be kept. Fix the problem as follows: - For internal toolchains: no change - For external toolchains: create a symlink ARCH_LIB_DIR->lib if (usr/)ARCH_LIB_DIR does not exist yet. Signed-off-by: -
Thomas De Schampheleire authored
The copy_toolchain_sysroot helper in toolchain/helpers.mk performs an rsync of various directories from the extracted external toolchain to the corresponding directory in staging. The relevant (simplified) snippet is: for i in etc $${ARCH_LIB_DIR} sbin usr usr/$${ARCH_LIB_DIR}; do \ rsync -au --chmod=u=rwX,go=rX --exclude 'usr/lib/locale' \ --exclude '/lib/' --exclude '/lib32/' \ --exclude '/lib64/' \ $${ARCH_SYSROOT_DIR}/$$i/ $(STAGING_DIR)/$$i/ ; \ done ; \ The exclusion logic of lib/lib32/lib64 has originally been added by commit 5628776c with the purpose of only copying the relevant usr/lib* directory from the toolchain to staging, instead of all. For example, if ARCH_LIB_DIR is 'lib64', then only usr/lib64 would be copied and usr/lib and usr/lib32 are ignored. It works by ignoring any lib/lib32/lib64 subdirectory on the rsync of 'usr' and then separately copying usr/{lib,lib32,lib64} as appropriate. (The exclusion rules only have impact on the files beneath the main source directory.) However, ARCH_LIB_DIR can take other values than (lib, lib32, lib64), for example lib32-fp or lib64-fp (Octeon III toolchain with -march=octeon3). In the existing code, the rsync for 'usr' would then already copy these lib directories, and the next rsync for 'usr/$${ARCH_LIB_DIR}' does nothing. By itself, this is not a very big problem: the staging directory simply has some extra directories. However, a subsequent patch will create a staging symlink from $${ARCH_LIB_DIR} to lib. The first rsync would then overwrite that symlink with the real directory usr/$${ARCH_LIB_DIR} from the toolchain, which is not correct. Assuming the patch that creates the symlink ARCH_LIB_DIR->lib is applied, the original situation after 'make clean toolchain' with an ARCH_LIB_DIR=lib32-fp is: $ ls -ld output/staging/{,usr/}lib* output/target/{usr/,}lib* drwxr-xr-x 2 4096 May 26 2015 output/staging/lib lrwxrwxrwx 1 3 Jan 20 13:47 output/staging/lib32 -> lib lrwxrwxrwx 1 3 Jan 20 13:47 output/staging/lib32-fp -> lib drwxr-xr-x 2 4096 Jan 20 13:47 output/staging/usr/lib lrwxrwxrwx 1 3 Jan 20 13:47 output/staging/usr/lib32 -> lib drwxr-xr-x 4 4096 May 26 2015 output/staging/usr/lib32-fp drwxr-xr-x 4 4096 May 26 2015 output/staging/usr/lib64-fp drwxr-xr-x 4 4096 May 26 2015 output/staging/usr/libexec drwxr-xr-x 3 4096 May 26 2015 output/staging/usr/libexec32 drwxr-xr-x 3 4096 May 26 2015 output/staging/usr/libexec32-fp drwxr-xr-x 3 4096 May 26 2015 output/staging/usr/libexec64-fp drwxr-xr-x 2 4096 Jan 20 13:48 output/target/lib lrwxrwxrwx 1 3 Jan 20 13:47 output/target/lib32 -> lib lrwxrwxrwx 1 3 Jan 20 13:47 output/target/lib32-fp -> lib drwxr-xr-x 2 4096 Jan 20 13:48 output/target/usr/lib lrwxrwxrwx 1 3 Jan 20 13:47 output/target/usr/lib32 -> lib lrwxrwxrwx 1 3 Jan 20 13:47 output/target/usr/lib32-fp -> lib Notice how usr/lib32-fp is not a symlink but a directory, and the presence of an unnecessary directory usr/lib64-fp. This patch improves the rsync exclusion rules by excluding any lib* directory on the first rsync. As this would also exclude any libexec/libexec32/... directory, explicitly include them first (first match takes precedence). This (as is already the case today) results in more usr/libexec* directories than needed, but it is not touched by this patch. With the fix applied, the situation becomes: drwxr-xr-x 2 4096 May 26 2015 output/staging/lib lrwxrwxrwx 1 3 Jan 20 14:27 output/staging/lib32 -> lib lrwxrwxrwx 1 3 Jan 20 14:27 output/staging/lib32-fp -> lib drwxr-xr-x 4 4096 May 26 2015 output/staging/usr/lib lrwxrwxrwx 1 3 Jan 20 14:27 output/staging/usr/lib32 -> lib lrwxrwxrwx 1 3 Jan 20 14:27 output/staging/usr/lib32-fp -> lib drwxr-xr-x 4 4096 May 26 2015 output/staging/usr/libexec drwxr-xr-x 3 4096 May 26 2015 output/staging/usr/libexec32 drwxr-xr-x 3 4096 May 26 2015 output/staging/usr/libexec32-fp drwxr-xr-x 3 4096 May 26 2015 output/staging/usr/libexec64-fp drwxr-xr-x 2 4096 Jan 20 14:27 output/target/lib lrwxrwxrwx 1 3 Jan 20 14:27 output/target/lib32 -> lib lrwxrwxrwx 1 3 Jan 20 14:27 output/target/lib32-fp -> lib drwxr-xr-x 2 4096 Jan 20 14:27 output/target/usr/lib lrwxrwxrwx 1 3 Jan 20 14:27 output/target/usr/lib32 -> lib lrwxrwxrwx 1 3 Jan 20 14:27 output/target/usr/lib32-fp -> lib For cases where ARCH_LIB_DIR is one of lib, lib32 or lib64 this fix makes no difference, and likewise for internal toolchains. Signed-off-by: -
Thomas De Schampheleire authored
The copy_toolchain_sysroot helper in toolchain/helpers.mk performs an rsync of various directories from the extracted external toolchain to the corresponding directory in staging. The relevant (simplified) snippet is: for i in etc $${ARCH_LIB_DIR} sbin usr usr/$${ARCH_LIB_DIR}; do \ rsync -au --chmod=u=rwX,go=rX --exclude 'usr/lib/locale' \ --exclude lib --exclude lib32 --exclude lib64 \ $${ARCH_SYSROOT_DIR}/$$i/ $(STAGING_DIR)/$$i/ ; \ done ; \ The exclusion logic of lib/lib32/lib64 has been added by commit 5628776c with the purpose of only copying the relevant usr/lib* directory from the toolchain to staging, instead of all. For example, if ARCH_LIB_DIR is 'lib64', then only usr/lib64 would be copied and usr/lib and usr/lib32 are ignored. It works by ignoring any lib/lib32/lib64 subdirectory on the rsync of 'usr' and then separately copying usr/{lib,lib32,lib64} as appropriate. (The exclusion rules only have impact on the files beneath the main source directory.) However, on the rsync of 'usr', ANY of the following directories AND files would be excluded: lib/ lib lib32/ foobar/something/lib/ something-else/lib64/ while it is only the intention to skip directories directly under usr. Therefore, add a leading (to restrict the scope to first-level) and trailing (to restrict to directories) slash to the exclude pattern. From 'man rsync': - if the pattern starts with a / then it is anchored to [..] the root of the transfer. - if the pattern ends with a / then it will only match a directory, not a regular file, symlink, or device. Signed-off-by: -
Bernd Kuhls authored
Fixes http://autobuild.buildroot.net/results/0cd/0cd47d7e6a49c268b57981ae8bb9abe4c4a183c7/ http://autobuild.buildroot.net/results/34b/34b0bea52bd7e65a927142dc0e1f28f85629c634/ [Thomas: adjust patch format.] Signed-off-by:
-
Bernd Kuhls authored
Signed-off-by:
-
Peter Korsgaard authored
It hasn't been updated since it was added in 2008, and nowadays things kind of stuff should be handled with genimage. Signed-off-by: -
Bernd Kuhls authored
Fixes http://autobuild.buildroot.net/results/530/53003be0dc2cb76d497a167023c5c45666fd00b4/ http://autobuild.buildroot.net/results/b23/b2393cd50c20da919d6111e15b78d12cc784841f/ Signed-off-by:
-
Yann E. MORIN authored
Signed-off-by:
"Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by:
-
Yann E. MORIN authored
Currently, makedevs will query the host's /etc/passwd and /etc/group to resolve usernames and group names. This is inherently flawed, as we can never guarantee that the UIDs will be the same on the target as on the host, or even whether a particular user does exist on the host. This is because getpwnam() and getgrnam() will forcibly read the system's /etc/passwd and /etc/group, and there is no way to tell them to look anywhere else. However, we can use fgetpwent() and fgetgrent() instead, for which we can pass a FILE* stream to read from to get the entries. This means we must implement the scanning-loop ourselves, but fortunately, that's pretty trivial to do. [Peter: swap errno / return value check, use bb_perror_msg_and_die, code style] Signed-off-by:
-
Yann E. MORIN authored
We will need the users and groups to get defined before we can use them from makedevs. Signed-off-by:
-
Gustavo Zacarias authored
Fixes: http://autobuild.buildroot.net/results/a6f/a6f6502e55fd68803f3ff8b4b76cce6601e101db/ Signed-off-by:
Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by:
-
Gustavo Zacarias authored
Signed-off-by:
-
- Jan 31, 2016
-
-
Bernd Kuhls authored
Fixes http://autobuild.buildroot.net/results/33c/33cac2bda4890b6050c71734b2c36a77db3d3a09/ http://autobuild.buildroot.net/results/9b5/9b56c1eb7a790d6df6665e8592004f20ed3f0693/ Signed-off-by:
-
Bernd Kuhls authored
Signed-off-by:
-
Bernd Kuhls authored
Upstream apparently updated their tarball http://thread.gmane.org/gmane.comp.lib.uclibc.buildroot/122226/focus=138335 Issue reported upstream: https://github.com/flot/flot/issues/1484 Signed-off-by:
-
Bernd Kuhls authored
Removed autoreconf and both patches after upstream commits: http://git.savannah.gnu.org/cgit/lightning.git/commit/configure.ac?id=e98640e1ac160034fe65346f68c5ade90d6b2032 http://git.savannah.gnu.org/cgit/lightning.git/commit/?id=361caf28545aa0c2b2ab8d1cbd334fbdd952f373 Signed-off-by:
-
Bernd Kuhls authored
Fixes http://autobuild.buildroot.net/results/aee/aee411047265bf205f8990a3d0d2310decb5fd19/ http://autobuild.buildroot.net/results/9a9/9a96fdd2b52a75b348b46696c7f8b427f2d987c2/ http://autobuild.buildroot.net/results/2e1/2e155f2f57fd035362ad1b414f42e1c2b5de844b/ http://autobuild.buildroot.net/results/f62/f62d3830c594d9169fa9b9df5212f190d676fab9/ Signed-off-by:
-
Bernd Kuhls authored
Removed patch applied upstream: http://sourceforge.net/p/oprofile/oprofile/ci/f357d40c9f64f3ea2dccf5f9abdff84b2ac62e6f/ Signed-off-by:
-
Bernd Kuhls authored
Updated _SITE after closure of gitorious.org. Signed-off-by:
-
Bernd Kuhls authored
Removed patch applied upstream: https://github.com/qpdf/qpdf/commit/857bb208d338e117f2a864407e34de76da360d8a Signed-off-by:
-
Julien BOIBESSOT authored
Signed-off-by:
Julien BOIBESSOT <julien.boibessot@armadeus.com> [Thomas: simplify exit logic of post-image script.] Signed-off-by:
-
Bernd Kuhls authored
Switch to upstream tarball, remove autoreconf, add hash. Upstream expects the boost unit tests being activated by default: http://sigrok.org/gitweb/?p=pulseview.git;a=blobdiff;f=CMakeLists.txt;h=77b0137db22b7b6cab80d8aee7c97fecb8c542bf;hp=a82953cc166141af626ace0e5d2b3a285bf20eea;hb=f513bec599b8d626f914aa804a01325914bdb5e9;hpb=8ada6ef1319fa11fd594a34853967c1f9688913b Add some logic to pulseview.mk to disable them if needed. Signed-off-by:
-
Bernd Kuhls authored
Switch to upstream tarball, remove autoreconf, add hash. Signed-off-by:
-
Bernd Kuhls authored
Switch to upstream tarball, remove autoreconf, add hash, fix typo. Signed-off-by:
-
Bernd Kuhls authored
Fixes http://autobuild.buildroot.net/results/afc/afcea2068d5b0ba707aa90339401550602103ca7/ http://autobuild.buildroot.net/results/a4d/a4dab61fb39dd642f85fad20972a0a4572af9a73/ and others Signed-off-by:
-
Bernd Kuhls authored
Switch to upstream tarball, remove autoreconf, add hash. Signed-off-by:
-
Bernd Kuhls authored
Switch to upstream tarball, remove autoreconf. Signed-off-by:
-
Bernd Kuhls authored
Fixes this musl build error: TermBuffer.cpp: In member function ‘virtual scx::Condition scx::TermBuffer::read(void*, int, int&)’: TermBuffer.cpp:83:10: error: ‘CEOT’ was not declared in this scope case CEOT: ^ TermBuffer.cpp:123:10: error: ‘CERASE’ was not declared in this scope case CERASE: // Backspace ^ The autobuilders did not catch this specific error yet because they failed earlier with other packages, but I am continuing the build based on the defconfig from: http://autobuild.buildroot.net/results/6cc/6cc0f8c067e07deea688b9b97284601a596b898c/ - added hash - removed 0001-fix-ssl-libs-ordering.patch, applied upstream: https://github.com/sconemad/sconeserver/commit/ffb69ca18fd03d0dc976696144d215b3a8555155 - disabled markdown module because its git submodule cmark ( https://github.com/sconemad/sconeserver/tree/master/markdown ) has no cross-compile support provided by the sconeserver build system: make[4]: Entering directory '/home/bernd/buildroot/br3/output/build/sconeserver-c4b8e14f6e9e06cbff5b4195f69d6fce9391a1cd/markdown/cmark' mkdir -p build; \ cd build; \ cmake .. \ -G "Unix Makefiles" \ -DCMAKE_BUILD_TYPE= \ -DCMAKE_INSTALL_PREFIX=/usr/local -- The C compiler identification is GNU 5.3.1 -- The CXX compiler identification is GNU 5.3.1 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works [...] Signed-off-by: -
Bernd Kuhls authored
According to https://gitweb.torproject.org/tor.git/plain/ReleaseNotes?id=tor-0.2.7.6 "Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series." so this patch bumps to the stable 2.7 series. This patch also fixes a musl build error not yet found by the autobuilders: CC src/common/workqueue.o src/common/sandbox.c:51:25: fatal error: bits/signum.h: Datei oder Verzeichnis nicht gefunden #include <bits/signum.h> ^ Signed-off-by:
-
Bernd Kuhls authored
Removed patch applied upstream: http://git.savannah.gnu.org/cgit/gpsd.git/commit/?id=3e25e2167beb3936de3986fad9b6c9bdec82b81f 0001-Fix-build-against-musl-libc.patch is also not needed anymore after this commit: http://git.savannah.gnu.org/cgit/gpsd.git/commit/?id=95c99f69e026e8c57aecba545e51c97f3b284e75 The upstream commit included in this version bump http://git.savannah.gnu.org/cgit/gpsd.git/commit/libgps.pc.in?id=772eedf8a13c2c0468b1fd94beb5406dbfcb3b6e fixes a build error with the location module of the updated sconeserver package included in this patch series: ../libtool: line 7486: cd: lib: No such file or directory libtool: error: cannot determine absolute directory name of 'lib' Makefile:428: recipe for target 'location.la' failed make[3]: *** [location.la] Error 1 Signed-off-by:
-
