Go to file
David Owens 3ab5dfb548 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>
2018-07-18 17:18:12 +02:00
arch
board imx/post-image: Allow flashing u-boot-dtb.imx in the SD card 2018-07-18 11:47:06 +02:00
boot
configs configs/imx7d-sdb: Add new defconfig 2018-07-18 11:54:58 +02:00
docs
fs
linux linux: bump default to version 4.17.7 2018-07-17 21:50:05 +02:00
package libglib2: Avoid absolute path to python in shebang 2018-07-18 17:18:12 +02:00
support
system
toolchain
utils
.defconfig
.flake8
.gitignore
.gitlab-ci.yml .gitlab-ci.yml: update with the addition of olimex_a10_olinuxino_lime_defconfig 2018-07-18 11:57:42 +02:00
.gitlab-ci.yml.in
CHANGES
Config.in
Config.in.legacy
COPYING
DEVELOPERS DEVELOPERS: add bluez-alsa to Jörg Krause 2018-07-18 15:15:25 +02:00
Makefile
Makefile.legacy
README

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