[Buildroot] [PATCH 1/1] libglib2: Avoid absolute path to python in shebang

[Thomas Petazzoni]

Hello,

On Thu, 12 Jul 2018 11:37:34 -0500, David Owens wrote:
> 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 at rockwellcollins.com>
> Signed-off-by: David Owens <david.owens at rockwellcollins.com>
> ---
>  ...t-hardcode-python-path-into-various-tools.patch | 48 ++++++++++++++++++++++
>  1 file changed, 48 insertions(+)
>  create mode 100644 package/libglib2/0004-Do-not-hardcode-python-path-into-various-tools.patch

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com