All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Ross Burton <ross@burtonini.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/4] help2man: rewrite recipe
Date: Fri, 17 Jul 2020 07:14:29 +0100	[thread overview]
Message-ID: <b9cce6cf64c1afa1f389262858bc5b0dab04d6f3.camel@linuxfoundation.org> (raw)
In-Reply-To: <20200716115546.3724268-2-ross@burtonini.com>

On Thu, 2020-07-16 at 12:55 +0100, Ross Burton wrote:
> From: Ross Burton <ross.burton@arm.com>
> 
> Instead of being explicitly native, use BBCLASSEXTEND.
> 
> No need to explicitly depend on autoconf-native automake-native,
> because
> the autotools class does that.
> 
> Don't explicitly disable NLS, but use the gettext class.
> 
> As this recipe isn't needed in early build anymore there's no need to
> avoid reconfiguring.
> 
> Signed-off-by: Ross Burton <ross.burton@arm.com>
> ---
>  ...2man-native_1.47.15.bb => help2man_1.47.15.bb} | 15 ++++++-------
> --
>  1 file changed, 6 insertions(+), 9 deletions(-)
>  rename meta/recipes-devtools/help2man/{help2man-native_1.47.15.bb =>
> help2man_1.47.15.bb} (66%)

https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/2185

configure: error: perl module Locale::gettext required

(from no-x11 world build)

Cheers,

Richard


  reply	other threads:[~2020-07-17  6:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 11:55 [PATCH 1/4] autotools: don't special-case help2man-native for dependencies Ross Burton
2020-07-16 11:55 ` [PATCH 2/4] help2man: rewrite recipe Ross Burton
2020-07-17  6:14   ` Richard Purdie [this message]
     [not found]   ` <1622758F3BA9F568.2727@lists.openembedded.org>
2020-07-17  6:15     ` [OE-core] " Richard Purdie
2020-07-16 11:55 ` [PATCH 3/4] flex: fix build with autoconf 2.70 Ross Burton
2020-07-16 11:55 ` [PATCH 4/4] nasm: " Ross Burton

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=b9cce6cf64c1afa1f389262858bc5b0dab04d6f3.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross@burtonini.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.