Go to file
David Owens fdc2097427 libglib2: Avoid absolute path to python in shebang
When the output directory is nested under a long path name, calling the
gdbus-codegen, glib-genmarshal, or glib-mkenums scripts throws the
error:

> '/usr/bin/env: /...: No such file or directory'

This is because libglib2 uses the absolute path to the python
interpreter for its shebang statements, and shebangs have a max length
of 127 chars[1]. A long absolute path will be cut off and appear as a
missing file.

Since the host Python is present in the $PATH passed to all packages, we
can copy the workaround from Yocto and just use the python interpreter
in $PATH[2]. However, 'python' is used instead of 'python3' as the
scripts are compatible with both.

[1] https://linux.die.net/man/2/execve
[2] http://cgit.openembedded.org/openembedded-core/commit/?id=eef7883587acc933d6f34b559ec03ff84d18573b

Signed-off-by: Brandon Maier <brandon.maier@rockwellcollins.com>
Signed-off-by: David Owens <david.owens@rockwellcollins.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
(cherry picked from commit 3ab5dfb548)
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-07-19 23:43:11 +02:00
arch Revert "arch/arm: add cortex-m7 core" 2018-05-20 19:13:29 +02:00
board board/minnowboard: add CONFIG_IGB in Linux kernel config 2018-07-19 23:31:51 +02:00
boot uboot: don't override HOSTCC/HOSTLDFLAGS for kconfig 2018-07-18 23:37:10 +02:00
configs configs/raspberrypi3_defconfig: increase filesystem size 2018-07-19 20:03:35 +02:00
docs docs/manual: fix scancpan path 2018-07-17 09:23:00 +02:00
fs fs: ensure hard links in TARGET_DIR are correctly copied for filesystem input 2018-05-27 23:46:29 +02:00
linux linux: automatically set CONFIG_PERF_EVENTS when perf is enabled 2018-07-19 19:57:23 +02:00
package libglib2: Avoid absolute path to python in shebang 2018-07-19 23:43:11 +02:00
support support/dependencies/dependencies.sh: add details for Redhat/Fedora 2018-07-19 12:13:55 +02:00
system skeleton: add /dev/fd, /dev/std{in, out, err} symlinks for static /dev on readonly rootfs 2018-05-01 21:53:45 +02:00
toolchain toolchain: allow disabling packages affected by gcc bug 85180 2018-05-30 23:23:21 +02:00
utils utils/test-pkg: log the output of merge-config 2018-07-19 23:27:56 +02:00
.defconfig arch: remove support for sh64 2016-09-08 22:15:15 +02:00
.flake8 .flake8: ignore utils/diffconfig 2018-03-13 22:37:54 +01:00
.gitignore
.gitlab-ci.yml .gitlab-ci.yml: update after removal of freescale defconfigs 2018-05-06 17:36:37 +02:00
.gitlab-ci.yml.in .gitlab-ci.yml: extend check-package test to Config.* files 2018-04-01 10:16:35 +02:00
CHANGES Update for 2018.05 2018-06-01 22:22:57 +02:00
Config.in Config.in: add BR2_HOST_GCC_AT_LEAST_8 2018-05-02 14:50:14 +02:00
Config.in.legacy libmediaart: rename options to have proper prefix 2018-05-21 23:13:52 +02:00
COPYING COPYING: add exception about patch licensing 2016-02-26 19:50:13 +01:00
DEVELOPERS DEVELOPERS: update datacom email addresses 2018-05-25 08:40:14 +02:00
Makefile Update for 2018.05 2018-06-01 22:22:57 +02:00
Makefile.legacy Remove BR2_DEPRECATED 2016-10-15 23:14:45 +02:00
README README: add reference to submitting-patches 2016-02-01 19:16:08 +01:00

Buildroot is a simple, efficient and easy-to-use tool to generate embedded
Linux systems through cross-compilation.

The documentation can be found in docs/manual. You can generate a text
document with 'make manual-text' and read output/docs/manual/manual.text.
Online documentation can be found at http://buildroot.org/docs.html

To build and use the buildroot stuff, do the following:

1) run 'make menuconfig'
2) select the target architecture and the packages you wish to compile
3) run 'make'
4) wait while it compiles
5) find the kernel, bootloader, root filesystem, etc. in output/images

You do not need to be root to build or run buildroot.  Have fun!

Buildroot comes with a basic configuration for a number of boards. Run
'make list-defconfigs' to view the list of provided configurations.

Please feed suggestions, bug reports, insults, and bribes back to the
buildroot mailing list: buildroot@buildroot.org
You can also find us on #buildroot on Freenode IRC.

If you would like to contribute patches, please read
https://buildroot.org/manual.html#submitting-patches