- 06 Jul, 2017 13 commits
-
-
Thomas Petazzoni authored
This file is not a package per-se, it includes other .mk files that are packages. Signed-off-by:Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-
Thomas Petazzoni authored
The waf package infrastructure was not known by the pkg-stats script, so let's add it. Signed-off-by: -
Ricardo Martincoski authored
With 2000+ packages it's not trivial to identify i.e.: - all packages that don't have a hash file; - all packages that have patches; - all packages that have code style warnings; User experience can be improved by dynamically sorting the resulting table. There is an open-source solution that does that in the client-side and requires minimal changes to our script: sorttable.js. The script is MIT licensed as stated in its website. Also add a hint to the user that the table can be sorted. Signed-off-by:
Ricardo Martincoski <ricardo.martincoski@gmail.com> Cc: Arnout Vandecappelle <arnout@mind.be> Signed-off-by:
-
Yegor Yefremov authored
The needed functionality is already included into Python 3.6.x, so these files can be now compiled without errors. Signed-off-by:
Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by:
-
Yegor Yefremov authored
Signed-off-by:
-
Yegor Yefremov authored
Changing setup type to setuptools avoids installing as zipped .egg Signed-off-by:
-
Jörg Krause authored
Signed-off-by:
Jörg Krause <joerg.krause@embedded.rocks> Signed-off-by:
-
Thomas Petazzoni authored
Since there is quite some duplication in the variables to be passed in the make environment and as make options between the build and install steps, this commit introduces LINUXPTP_MAKE_ENV and LINUXPTP_MAKE_OPTS to avoid the duplication. Signed-off-by: -
Romain Naour authored
incdefs.sh try to define some flags with user_flags() and kernel_flags() functions. The later is looking at the kernel headers installed on the host when KBUILD_OUTPUT is not set. If no kernel headers are installed on the host, the grep fail and HAVE_ONESTEP_SYNC is not set on the command line: see: grep: /usr/include/linux/net_tstamp.h: No such file or directory So the missing.h define HWTSTAMP_TX_ONESTEP_SYNC which is also present in the kernel headers installed in STAGING_DIR (toolchain w/ headers >= 3.2). Indeed KBUILD_OUTPUT is empty because it's reset in the makefile, so move KBUILD_OUTPUT in the enviroment while calling "make"/ Also set KBUILD_OUTPUT to STAGING_DIR to find net_tstamp.h. While at it, use the same arguments for BUILD_CMDS and INSTALL_TARGET_CMDS. Thanks to Yann for the live review during the Buildroot summer camp. Fixes: http://autobuild.buildroot.net/results/364/36470db2c262d2e1fda5144a08cfe221831e093e Signed-off-by:
Romain Naour <romain.naour@smile.fr> Cc: Petr Kulhavy <brain@jikos.cz> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by:
-
Romain Naour authored
Thanks to Yann for the live review during the Buildroot summer camp. Signed-off-by:
-
Baruch Siach authored
Change site to https to avoid a redirection. Signed-off-by:
Baruch Siach <baruch@tkos.co.il> Signed-off-by:
-
Thomas Petazzoni authored
The XVISOR_ARCH check added in commit 117fd5df ("xvisor: fix build on AArch64") broke Buildroot entirely on all architectures except ARM, AArch64 and x86-64, because the $(error ...) test was not enclosed inside a condition that made sure the xvisor package was enabled. This commit fixes that, and allows Buildroot to be usable again on all architectures. Signed-off-by:
Peter Korsgaard <peter@korsgaard.com>
-
Baruch Siach authored
Commit 32bec8ee (toolchain-external: copy ld*.so* for all C libraries) removed the definition of TOOLCHAIN_EXTERNAL_MUSL_LD_LINK. Remove also the reference to it. Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by:
-
- 05 Jul, 2017 27 commits
-
-
Thomas Petazzoni authored
In commit 32bec8ee ("toolchain-external: copy ld*.so* for all C libraries") we changed how the musl dynamic linker symbolic link was being created. Instead of having specific logic in Buildroot, we switched to simply copying the ld*.so.* symbolic link from staging to target, as well as the target of this symbolic link. However, it turns out that by default, musl creates its dynamic linker symbolic link with an absolute path as the target of the link: /lib/libc.so. Therefore, external Musl toolchains built with Buildroot look like this: lrwxrwxrwx 1 thomas thomas 12 Jul 4 19:46 ld-musl-armhf.so.1 -> /lib/libc.so The principle of the copy_toolchain_lib_root function, which is used to copy libraries from staging to target, is to copy symbolic links and follow their targets. In this case, it means we end up copying /lib/libc.so (from the host machine) into the target folder. From there on, there are two cases: 1. /lib/libc.so exists in your host system. It gets copied to the target. But later on, Buildroot also copies /lib/libc.so from staging to target, overwriting the bogus libc.so. So everything works fine, even though it's admittedly ugly. 2. /lib/libc.so doesn't exist in your host system. In this case, the build fails with no clear error message. This problem does not happen with Musl toolchains built by Crosstool-NG, because Crosstool-NG replaces the absolute target of the dynamic linker symbolic link by a relative path. However, since we want to support existing Buildroot Musl toolchains and generally work with the fact that Musl by default installs an absolute symlink, the following commit improves the copy_toolchain_sysroot function to replace symbolic links with an absolute destination to use a relative destination. I.e, in staging, the ld-musl-armhf.so.1 symbolic link looks like this: lrwxrwxrwx 1 thomas thomas 14 Jul 5 22:59 output/staging/lib/ld-musl-armhf.so.1 -> ../lib/libc.so Fixes: http://autobuild.buildroot.net/results/ce80264575918a8f71d9eab1091c21df85b65b1a/ Signed-off-by:
-
Thomas Petazzoni authored
Xvisor was failing to build on AArch64 with: package/xvisor/xvisor.mk:60: *** No Xvisor defconfig name specified, check your BR2_PACKAGE_XVISOR_DEFCONFIG setting. Stop. The first problem is that the Config.in file had a typo: it was using BR2_AARCH64 instead of BR2_aarch64, and therefore the BR2_PACKAGE_XVISOR_DEFCONFIG variable had no value. Once this is fixed, another problem occurs: the ARCH variable needs to be specified as "arm" for XVisor, for both ARM and AArch64. Therefore, a XVISOR_ARCH variable is introduced, which is calculated according to the Buildroot configuration options. Only x86-64, arm and aarch64 are supported by Xvisor currently, so it remains simple. Fixes: http://autobuild.buildroot.net/results/1719a63ff257f13634a06a14327abfb327984101/ Signed-off-by:
-
Rahul Bedarkar authored
Signed-off-by:
Rahul Bedarkar <rahulbedarkar89@gmail.com> Signed-off-by:
-
Rahul Bedarkar authored
Signed-off-by:
-
Rahul Bedarkar authored
Signed-off-by:
-
Rahul Bedarkar authored
Signed-off-by:
-
Rahul Bedarkar authored
Signed-off-by:
-
Rahul Bedarkar authored
Signed-off-by:
-
Rahul Bedarkar authored
Signed-off-by:
-
Romain Naour authored
kvazaar is affected by three different build issues on PowerPC and related architectures: - On PowerPC64, the build fails due to the use of a deprecated vec_lvsl() function: strategies/altivec/picture-altivec.c: In function ‘reg_sad_altivec’: strategies/altivec/picture-altivec.c:43:5: error: vec_lvsl is deprecated for little endian; use assignment for unaligned loads and stores [-Werror=deprecated] perm1 = vec_lvsl(0, &data1[y * stride1]); ^~~~~ This bug has been reported upstream at: https://github.com/ultravideo/kvazaar/issues/172 - On PowerPC 8548, the build fails due to mixing AltiVec and E500 instructions: strategies/altivec/picture-altivec.c:1:0: error: AltiVec and E500 instructions cannot coexist This bug has been reported upstream at: https://github.com/ultravideo/kvazaar/issues/173 - On PowerPC e500mc, because Altivec is not supported on this target: strategies/altivec/picture-altivec.c:1:0: error: AltiVec not supported in this target This bug has been reported upstream at: https://github.com/ultravideo/kvazaar/issues/174 Fixes: http://autobuild.buildroot.net/results/486/486757f04bc73736b64d18c3298216280be897b1 http://autobuild.buildroot.net/results/45d/45d22c9f2f5b593bed286319105c82cbc3396835 http://autobuild.buildroot.net/results/76c/76c76191f84748326d76fe0cc89456a72738a06b Signed-off-by:
-
Bernd Kuhls authored
Signed-off-by:
Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by:
-
Bernd Kuhls authored
Signed-off-by:
-
Adrián Pérez de Castro authored
[Peter: reword commit message] Signed-off-by:
Adrian Perez de Castro <aperez@igalia.com> Signed-off-by:
-
Chakra Divi authored
Add initial support for nanopi-m1 board with below features - U-Boot 2017.07-rc1 - Linux 4.11.5 - Default packages from buildroot Signed-off-by:
Chakra Divi <chakra@openedev.com> Signed-off-by:
-
Arnout Vandecappelle authored
In commit b3cc7e65 , the definition of the DESTDIR variable was moved down into the loop that follows symlinks in the libraries that are copied to target. However, the corresponding mkdir was not moved down, so that no directories are ever created. In practice, this mkdir is normally redundant since the directories should already have been created as part of creating STAGING_DIR. Still, the current situation is clearly wrong, so fix it by moving the mkdir down to after the assignment to DESTDIR. While we're at it, also remove a redundant empty line. It's a leftover from when a lot of variables were declared above. Signed-off-by:
Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by:
-
Adrián Pérez de Castro authored
This simply updates to the latest stable release. WebKitGTK+ versions in the 2.1x series avoid bumping the dependencies in order to allow distributions to provide updates, therefore no new dependencies are needed. Signed-off-by:
-
Arnout Vandecappelle authored
Signed-off-by:
-
Arnout Vandecappelle authored
Now all packages have been updated to install things in $(HOST_DIR)/lib instead of $(HOST_DIR)/usr/lib, there should no longer be any reason to have $(HOST_DIR)/usr/lib in the RPATH, so we don't allow it any more. Signed-off-by:
-
Arnout Vandecappelle authored
The tools are now installed in host/bin instead of host/usr/bin. Signed-off-by:
-
Stefan Sørensen authored
Fixes: http://autobuild.buildroot.net/results/cfb3a591391d90762a326d91af3ec502a6161ac5 Signed-off-by:
Stefan Sørensen <stefan.sorensen@spectralink.com> Signed-off-by:
-
Yann E. MORIN authored
This silences the annoying warning that there is no hash file for our own COPYING file. Also change the message so that it is more obvious what we're doing. Reported-by:
"Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Luca Ceresoli <luca@lucaceresoli.net> Signed-off-by:
-
Adrián Pérez de Castro authored
Signed-off-by:
-
Fabio Estevam authored
Signed-off-by:
Fabio Estevam <festevam@gmail.com> Signed-off-by:
-
Arnout Vandecappelle authored
The host build passes the --shebangdir configure option, the target build doesn't. With the removal of $(HOST_DIR)/usr, it is not clear if this should be /bin or /usr/bin or $(HOST_DIR)/bin. Looking at the source code, it turns out that this variable is not used at all, and /usr/bin doesn't appear anywhere in the installed files. Since it is not clear what this option should be set to, and it anyway doesn't do anything, remove it entirely. Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr> Signed-off-by:
-
Arnout Vandecappelle authored
policycoreutils has a pretty peculiar interpretation of DESTDIR and PREFIX. PREFIX is not consistently used: some installation paths and include paths are forced to $(DESTDIR)/usr/... . In other cases, PREFIX is indeed used. PREFIX defaults to $(DESTDIR)/usr Try to be a little bit more correct by passing both DESTDIR and PREFIX, both set to $(HOST_DIR). This is not a complete fix: some things are still installed in $(HOST_DIR)/usr - but nothing we care about (just manpages, systemd services, ...). More importantly, however, it still looks for e.g. D-Bus in $(DESTDIR)/usr/include/dbus-1.0. Still, it's better than nothing. Signed-off-by:
-
Arnout Vandecappelle authored
checkpolicy has a pretty peculiar interpretation of DESTDIR and PREFIX. PREFIX simply defaults to $(DESTDIR)/usr, and is used in the rest of the build system. DESTDIR isn't used any further. For the host installation, we don't want the usr part, so set PREFIX instead of DESTDIR. Signed-off-by:
-
Arnout Vandecappelle authored
libselinux has a pretty peculiar interpretation of DESTDIR and PREFIX. PREFIX is not consistently used: some installation paths are forced to $(DESTDIR)/usr/... . In other cases, PREFIX is indeed used. PREFIX defaults to $(DESTDIR)/usr. Try to be a little bit more correct by passing both DESTDIR and PREFIX, both set to $(HOST_DIR). This is not a complete fix: man pages are still installed in $(HOST_DIR)/usr - but we don't care about that. Also simplify the symlink creation, like how it's done in libsepol. Signed-off-by:
-
