From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: gtk+-native build problem
Date: Tue, 07 Sep 2010 12:34:05 +0200 [thread overview]
Message-ID: <4C86151D.50801@dresearch.de> (raw)
While running some builds for testing-next i hit a problem with gtk+-native.
The do_configure stage failed with "configure: error: *** Sorry,
cups-config present but cups/cups.h missing." (for details see
<http://tinderbox.openembedded.org/packages/734326/>).
I guess the problem is that at the build host cups is installed but not
cups-devel and gtk+-native somehow likes to use it.
Can someone have a look at it. May be a cups-dev dependency in gtk+.inc
fixes the problem?
Steffen
next reply other threads:[~2010-09-07 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 10:34 Steffen Sledz [this message]
2010-09-08 12:00 ` [PATCH] gtk+: fix configure problem for native build Steffen Sledz
2010-09-08 12:02 ` Graeme Gregory
2010-09-08 14:40 ` Steffen Sledz
2010-09-08 17:41 ` Khem Raj
2010-09-09 5:51 ` Steffen Sledz
2010-09-08 17:45 ` Khem Raj
2010-09-09 5:54 ` Steffen Sledz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C86151D.50801@dresearch.de \
--to=sledz@dresearch.de \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox