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 664588 - build: do not reset PKG_CONFIG_PATH= when building .gir
build: do not reset PKG_CONFIG_PATH= when building .gir
Status: RESOLVED DUPLICATE of bug 662708
Product: gtk-vnc
Classification: Other
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: gtk-vnc-maint
gtk-vnc-maint
Depends on:
Blocks:
 
 
Reported: 2011-11-22 20:00 UTC by Frederic Peters
Modified: 2011-12-13 13:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
build: do not reset PKG_CONFIG_PATH= when building .gir (1.36 KB, patch)
2011-11-22 20:01 UTC, Frederic Peters
none Details | Review

Description Frederic Peters 2011-11-22 20:00:16 UTC
src/Makefile.am sets PKG_CONFIG_PATH to $(top_builddir) but it does this
without preserving the content of that environment variable, making it
fail in jhbuild with an error such as:

  GEN    GtkVnc-2.0.gir
  Package gtk+-3.0 was not found in the pkg-config search path.
  Perhaps you should add the directory containing `gtk+-3.0.pc'
  to the PKG_CONFIG_PATH environment variable
  No package 'gtk+-3.0' found
  Package gtk+-3.0 was not found in the pkg-config search path.
  Perhaps you should add the directory containing `gtk+-3.0.pc'
  to the PKG_CONFIG_PATH environment variable
  Package 'gtk+-3.0', required by 'GTK-VNC', not found
  In file included from <stdin>:4:0:
  /scratch/jhbuild/src/gtk-vnc-0.4.4/src/vnccairoframebuffer.h:25:21: fatal error: gdk/gdk.h: No such file or directory
  compilation terminated.
Comment 1 Frederic Peters 2011-11-22 20:01:15 UTC
Created attachment 201947 [details] [review]
build: do not reset PKG_CONFIG_PATH= when building .gir
Comment 2 Christophe Fergeau 2011-12-08 07:57:27 UTC
This is a duplicate of the uncommitted patch from bug #662708
Comment 3 Christophe Fergeau 2011-12-13 13:37:42 UTC

*** This bug has been marked as a duplicate of bug 662708 ***