From: Peter Urbanec <openembedded-devel@urbanec.net>
To: Paul Gortmaker <paul.gortmaker@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] mozjs: fix build failure due to missing dependency on libxt
Date: Thu, 12 Feb 2015 14:56:41 +1100 [thread overview]
Message-ID: <54DC2479.7050507@urbanec.net> (raw)
In-Reply-To: <1423699224-19243-1-git-send-email-paul.gortmaker@windriver.com>
On 12/02/15 11:00, Paul Gortmaker wrote:
> Looking at the configure script, we see these invalid values are output
> when the autoconf test for X11 fails. That test fails in the following
> fashion:
...
> Since the package clearly has never been built in a no-X11 OE environment,
> we assume that all OE users to date are X11 users and hence simply add a
> dependency on libxt.
I've run into this problem quite a while ago. My fix for this was a
.bbappend file that passes --without-x to configure, since my target has
no X11.
next prev parent reply other threads:[~2015-02-12 3:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 0:00 [PATCH] mozjs: fix build failure due to missing dependency on libxt Paul Gortmaker
2015-02-12 3:56 ` Peter Urbanec [this message]
2015-02-13 6:56 ` Paul Gortmaker
2015-02-13 15:17 ` Burton, Ross
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=54DC2479.7050507@urbanec.net \
--to=openembedded-devel@urbanec.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.gortmaker@windriver.com \
/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