From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/5] texinfo/texinfo-dummy-native: Drop native path prefix
Date: Wed, 29 Jan 2020 11:59:59 +0000 [thread overview]
Message-ID: <10d77c789a51e9fdb089b2faf983414cc17fb20b.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1sqYswYbOA+N80sK3sELzPPCTymDna8bgSKETCvZROi2Fw@mail.gmail.com>
On Tue, 2020-01-28 at 18:00 -0800, Khem Raj wrote:
> it perhaps is the reason for most of failures seen here
>
> https://errors.yoctoproject.org/Errors/Build/97736/
>
> perhaps we need to explicitly inherit gettext in these recipes ?
These patches aren't quite working in master yet but those failures
look like they'd be solved with an "inherit texinfo" added to the
recipes.
Cheers,
Richard
next prev parent reply other threads:[~2020-01-30 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 15:16 [PATCH 1/5] bc: Use texinfo class Richard Purdie
2020-01-28 15:16 ` [PATCH 2/5] glibc-package.inc: Remove warnings about unpacked directories Richard Purdie
2020-01-28 15:16 ` [PATCH 3/5] texinfo/texinfo-dummy-native: Drop native path prefix Richard Purdie
2020-01-29 2:00 ` Khem Raj
2020-01-29 11:59 ` Richard Purdie [this message]
2020-01-29 16:02 ` Khem Raj
2020-01-28 15:16 ` [PATCH 4/5] texinfo: Only build texinfo when api-docs enabled Richard Purdie
2020-01-28 15:16 ` [PATCH 5/5] bitbake.conf/sanity: Drop makeinfo as being required on buildhost Richard Purdie
2020-01-28 15:58 ` [PATCH 1/5] bc: Use texinfo class Jacob Kroon
2020-01-28 16:18 ` Richard Purdie
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=10d77c789a51e9fdb089b2faf983414cc17fb20b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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