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 562885 - [scanner] command line option -L not working
[scanner] command line option -L not working
Status: RESOLVED DUPLICATE of bug 630993
Product: gobject-introspection
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gobject-introspection Maintainer(s)
gobject-introspection Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-12-01 16:59 UTC by Havoc Pennington
Modified: 2015-02-07 16:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Havoc Pennington 2008-12-01 16:59:08 UTC
I don't have a small simple test case to prove it, but with our app, it seems that if you try to build it in a non-jhbuild environment, but non-default prefix, the -L flags to g-ir-scanner are needed but don't get used.

When building a normal package, /usr/lib will be in the path anyway

In jhbuild, LD_LIBRARY_PATH is set anyway

So this only gets noticed if you build without jhbuild in a nonstandard prefix.

In that case, though, unclear that g-ir-scanner -L is doing anything.

This may be fixed, I thought I saw a related-looking patch go by.
Comment 1 Josselin Mouette 2009-09-24 10:51:39 UTC
Confirmed this is still here in 0.6.5. The library_paths variable is set but never used, so in the end the option is ignored.
Comment 2 Simon Feltman 2013-09-13 21:23:45 UTC

*** This bug has been marked as a duplicate of bug 630993 ***
Comment 3 André Klapper 2015-02-07 16:53:34 UTC
[Mass-moving gobject-introspection tickets to its own Bugzilla product - see bug 708029. Mass-filter your bugmail for this message: introspection20150207 ]