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 402995 - configure requires X connection
configure requires X connection
Status: RESOLVED WONTFIX
Product: pitivi
Classification: Other
Component: General
0.10.x
Other All
: Normal normal
: Git
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-31 21:49 UTC by jeff
Modified: 2007-02-02 15:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description jeff 2007-01-31 21:49:46 UTC 
Please describe the problem:
0.10.2 now requires an X connection to build due to the changes that were made in the configure script to detect PyGTK.  This is a problem for Fedora because the Fedora buildsystem does not have an X server running while the RPM package for PiTiVi is being built.  I'm the official maintainer of the PiTiVi package for Fedora - I've reverted the changes that were made to the PyGTK detection code for now, but I'd rather not maintain that indefinitely.

Steps to reproduce:
1. Unpack sources
2. unset DISPLAY
3. ./configure



Actual results:
checking for GTK python bindings... Traceback (most recent call last):

+ Trace 106947

  • File "<string>", line 6 in ?
  • File "/usr/lib/python2.4/site-packages/gtk-2.0/gtk/__init__.py", line 76 in ? 
    _init()
  • File "/usr/lib/python2.4/site-packages/gtk-2.0/gtk/__init__.py", line 64 in _init 
    _gtk.init_check()
RuntimeError: could not open display 
not found
configure: error: You need to have python gtk bindings >= 2.8.0 installed


Expected results:
Able to configure and build PiTiVi

Does this happen every time?
Yes.

Other information:
http://bugzilla.gnome.org/show_bug.cgi?id=382249
http://svn.gnome.org/viewcvs/pitivi/trunk/configure.ac?rev=836&r1=834&r2=836
Comment 1 Edward Hervey 2007-02-02 15:06:30 UTC 
Unfortunately, those changes are going to stay in, because they fix issues for many more people than ONE build system on which it fails.

Also, the issue it fixes is rather important (picking the correct python version/libraries).

I remember some other program which had the same issue (flumotion) and they fixed it by installing a fake X server on the build system. Maybe fedora might want to consider that.