From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] nasm: nasm has a build dependency on groff-native
Date: Wed, 18 Jul 2012 22:23:56 +0100 [thread overview]
Message-ID: <1342646636.513.53.camel@ted> (raw)
In-Reply-To: <20120718173922.GA20427@windriver.com>
On Wed, 2012-07-18 at 13:39 -0400, Amy Fong wrote:
> nasm has a build dependency on groff-native
>
> In one incident, there was a case where nasm-native compile phase failed
> with the following:
>
> +troff: can't find `DESC' file
> +troff: fatal error: sorry, I can't continue
>
> During this, groff-native was in the sysroot install phase.
> To remedy this, adding groff-native in nasm's dependency list.
>
> Signed-off-by: Amy Fong <amy.fong@windriver.com>
> ---
> nasm_2.07.bb | 2 ++
> 1 file changed, 2 insertions(+)
This patch doesn't apply against master which has version 2.10.01. I
made it apply in this case since it appears still relevant but please
check this in future.
Cheers,
Richard
prev parent reply other threads:[~2012-07-18 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 17:39 [PATCH] nasm: nasm has a build dependency on groff-native Amy Fong
2012-07-18 21:23 ` Richard Purdie [this message]
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=1342646636.513.53.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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 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.