From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH][meta-oe] dialog: use pkg-config to detect ncurses
Date: Thu, 19 Jun 2014 10:46:40 +0200 [thread overview]
Message-ID: <20140619084640.GM2117@jama> (raw)
In-Reply-To: <53A29E1D.9080307@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
On Thu, Jun 19, 2014 at 04:23:57PM +0800, Rongqing Li wrote:
>
>
> On 06/19/2014 03:34 PM, Koen Kooi wrote:
> >> +Subject: [PATCH] use pkg-config for ncurses detection. +
> >> >+Upstream-Status: Inappropriate [configuration]
> > Why is it inappropriate?
>
>
> I think we should fix the configure.in, but this configure.in can not
> work with oe-core, the dialog bb file runs configure directly, and
> I do this fix in configure directly, so it is Inappropriate
Can you please fix dialog-static as well? It probably doesn't even work with B!=S.
| DEBUG: Executing shell function do_configure
| gnu-configize: 'configure.ac' or 'configure.in' is required
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure (log file is located at /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/armv5te-oe-linux-gnueabi/dialog-static/1.1-20120706-r0/temp/log.do_configure.20677)
NOTE: recipe dialog-static-1.1-20120706-r0: task do_configure: Failed
Otherwise it will be PNBLACKLISTED this weekend (together with a lot of other unmaintained recipes)
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2014-06-19 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 4:46 [PATCH][meta-oe] dialog: use pkg-config to detect ncurses rongqing.li
2014-06-19 7:34 ` Koen Kooi
2014-06-19 8:23 ` Rongqing Li
2014-06-19 8:46 ` Martin Jansa [this message]
2014-06-19 8:51 ` Rongqing Li
2014-06-19 9:11 ` Martin Jansa
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=20140619084640.GM2117@jama \
--to=martin.jansa@gmail.com \
--cc=koen@dominion.thruhere.net \
--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