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 512981 - configure script checks for cups even when cross-compiling
configure script checks for cups even when cross-compiling
Status: RESOLVED DUPLICATE of bug 513826
Product: gtk+
Classification: Platform
Component: Backend: Win32
2.12.x
Other All
: Normal blocker
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2008-01-30 01:47 UTC by Alexis Wilke
Modified: 2008-02-02 07:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alexis Wilke 2008-01-30 01:47:13 UTC
Please describe the problem:
The configure scripts checks for the cups environment and finds cups-config (which I have on my Linux box--really only because samba requires it.)

Then it checks to see whether the cups/cups.h is present. It isn't since I do not develop with it.

But, really, what I'm doing here is cross-compile for Win32 using the mingw32 environment under Ubuntu. That works, but only after I set some weird CUPS_CONFIG variable to "no" (i.e. no cups.)

Here you should either test whether you are cross compiling and if so check the cross compiled folders properly or have a command line option saying --without-cups.


Steps to reproduce:
1. Have fun recompiling all the GTK+ dependencies with the mingw compiler
2. cd gtk+-2.12.6
3. ./configure ...

(I assume you know of the many variables you have to set, etc.)

Actual results:
configure breaks saying that cups-config exists but not cups/cups.h

Expected results:
I would expect a --without-cups flag so we can simply tell the configure script to forget about it.

The best would be to check whether you are cross-compiling and if so, check with the cross-compiling PATH instead of the default path (but I think this is an automake feature...)

Does this happen every time?
Yes. Every time.

Other information:
To bypass this problem, I use the following:

  export ac_cv_path_CUPS_CONFIG="no"

This works great for now, but of course is not a good solution!
Comment 1 Cody Russell 2008-02-02 07:43:30 UTC

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