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 377468 - Error in glib-java's macros/jg_common.m4 prevents all other java-gnome libraries from building
Error in glib-java's macros/jg_common.m4 prevents all other java-gnome librar...
Status: VERIFIED FIXED
Product: java-gnome
Classification: Bindings
Component: Bindings Core
Unmaintained
Other All
: Immediate blocker
: ---
Assigned To: java-gnome bindings maintainers
java-gnome bindings maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-20 18:26 UTC by Andrew Cowie
Modified: 2007-01-05 01:28 UTC
See Also:
GNOME target: 2.16.x
GNOME version: 2.15/2.16


Description Andrew Cowie 2006-11-20 18:26:22 UTC 
The attachment #74620 [details] to bug #360207 had bugs in the changes it made to the jg_common.m4 autoconf macros file. The result is that someone NOT building a package who doesn't specify the new --with-macrobasedir or --with-jardir options manually but rather wants the defaults gets a glib-java.pc file which has ${datarootdir} in it which is meaningless in a .pc file and which causes the build of cairo-java, libgtk-java, etc to fail.

AfC
Comment 1 Andrew Cowie 2006-11-20 18:29:31 UTC 
Workaround (solution?) appears to be:

a) using ${prefix}/share instead of ${datadir} as default

b) escaping the $ so that the literal gets through to the .pc file, rather than
the subsituted value.

Testing.

AfC
Comment 2 Andrew Cowie 2006-11-21 15:57:38 UTC 
Committed the fix discussed above to glib-java, and pushed out in release version 0.4.1

It was definitely a requirement in order to get libgtk-java 2.10.1 to build, but it remains unclear whether the others need it. It seems that they don't as their .pc files don't have hanging references to macrobasedir and whatnot.

AfC