After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 553724 - python interpretter path not patched in correctly
python interpretter path not patched in correctly
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: general
2.18.x
Other Mac OS
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2008-09-25 07:21 UTC by Daniel Macks
Modified: 2008-09-26 14:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel Macks 2008-09-25 07:21:31 UTC
The sed script in glib/Makefile.am that is supposed to paste in the python interpreter path into gtester-report is broken. The regexp match is for:

-e '1,1s|#!/usr/bin/env python\([0-9]\+\(\.[0-9]\+\)\?\)\?|#!${PYTHON}|' \

but gtester-report begins:

#! /usr/bin/env python

There's differnce of a whitespace after the shbang, which prevents the regexp from matching and therefore the installed gtester-report script still specifies:

#! /usr/bin/env python

instead of whatever PYTHON was determined during ./configure
Comment 1 Matthias Clasen 2008-09-26 14:31:05 UTC
2008-09-26  Matthias Clasen  <mclasen@redhat.com>

        Bug 553724 – python interpretter path not patched in correctly

        * glib/Makefile.am: Fix the sed magic to replace python.