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 727575 - Host paths leak into target when cross compiling
Host paths leak into target when cross compiling
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: build
unspecified
Other Linux
: Normal minor
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2014-04-04 01:17 UTC by Drew Moseley
Modified: 2018-05-24 16:23 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch to make configure.ac skip the readlink invocation when cross compiling. (1.17 KB, patch)
2014-04-04 01:17 UTC, Drew Moseley 		none Details | Review

Description Drew Moseley 2014-04-04 01:17:21 UTC 
Created attachment 273562 [details] [review]
Patch to make configure.ac skip the readlink invocation when cross compiling.

When building glib, the configure.ac script uses 'readlink' to convert relative paths to absolute.  For cross compiling this can result in paths being incorrect for the target system.

I'm building Yocto-based configurations.  On my build system /usr/lib64 is actually a symlink to /usr/lib.  For the 64-bit cross compiled target, readlink incorrectly translates /usr/lib64 to /usr/lib resulting in the path /usr/share/gdb/auto-load/usr/lib/libglib-2.0.so.0.3800.2-gdb.py rather than /usr/share/gdb/auto-load/usr/lib64/libglib-2.0.so.0.3800.2-gdb.py
Comment 1 Drew Moseley 2014-04-04 01:18:53 UTC 
This patch is not perfect as it simply does nothing to convert it to an absolute path but at least the host paths no longer leak into the target filesystem.
Comment 2 GNOME Infrastructure Team 2018-05-24 16:23:23 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/851.