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 343978 - autoconf's python not used in gmenu-simple-editor
autoconf's python not used in gmenu-simple-editor
Status: RESOLVED FIXED
Product: gnome-menus
Classification: Core
Component: general
2.14.x
Other Mac OS
: Normal normal
: ---
Assigned To: gnome-menus dummy account
gnome-menus dummy account
Depends on:
Blocks:
 
 
Reported: 2006-06-06 04:57 UTC by Daniel Macks
Modified: 2007-05-01 09:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gmenu-simple-editor obeys configure's python interp path (1.05 KB, patch)
2006-06-06 05:26 UTC, Daniel Macks
none Details | Review

Description Daniel Macks 2006-06-06 04:57:46 UTC
./configure finds the path to the python interpretter and its associated module directory, and this information is . As part of the gmenu-simple-editor.in -> gmenu-simple-editor processing, the module directory is patched in via @pyexecdir@, but the path to the python interp is left up to a runtime `env python`. That means the python used as runtime, "first 'python' in PATH" might not be the one against which the gnome-menus python bindings were compiled. Even if I explicitly pass PYTHON when running configure "use this specific python interp", `env python` is still being used instead.
Comment 1 Daniel Macks 2006-06-06 05:26:19 UTC
Created attachment 66808 [details] [review]
gmenu-simple-editor obeys configure's python interp path
Comment 2 Vincent Untz 2007-05-01 09:54:09 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.