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 667941 - gtk-vnc-0.5.0 fails to configure in out-of-source builds (GNUmakefile not found)
gtk-vnc-0.5.0 fails to configure in out-of-source builds (GNUmakefile not found)
Status: RESOLVED DUPLICATE of bug 668442
Product: gtk-vnc
Classification: Other
Component: general
0.5.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-vnc-maint
gtk-vnc-maint
Depends on:
Blocks:
 
 
Reported: 2012-01-15 02:48 UTC by Alexandre Rostovtsev
Modified: 2012-03-13 18:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alexandre Rostovtsev 2012-01-15 02:48:38 UTC
Due to commit 083daa73 ("Import GNULIB framework for checking code style / rules"), gtk-vnc fails when building out-of-source from a release tarball:

$ tar -xJf gtk-vnc-0.5.0.tar.xz
$ cd gtk-vnc-0.5.0
$ mkdir _build
$ cd _build
$ ../configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
[...]
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating tools/Makefile
config.status: creating examples/Makefile
config.status: creating plugin/Makefile
config.status: creating po/Makefile.in
config.status: creating vapi/Makefile
config.status: creating gvnc-1.0.pc
config.status: creating gvncpulse-1.0.pc
config.status: creating gtk-vnc-1.0.pc
config.status: creating gtk-vnc-2.0.pc
config.status: creating gtk-vnc.spec
config.status: creating mingw32-gtk-vnc.spec
config.status: creating config.h
config.status: linking ../GNUmakefile to GNUmakefile
config.status: error: ../GNUmakefile: file not found

Note that for in-source builds, configure works as expected.
Comment 1 Daniel P. Berrange 2012-03-13 18:48:46 UTC

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