From: Patrick Ohly <patrick.ohly@intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libtasn1: depends on yacc
Date: Thu, 02 Feb 2017 12:20:26 +0100 [thread overview]
Message-ID: <1486034426.14889.46.camel@intel.com> (raw)
In-Reply-To: <aeb5c3c0-339c-45e0-9e1e-bbad796e1a2b@gmail.com>
On Wed, 2017-02-01 at 08:56 -0800, Khem Raj wrote:
>
> On 1/31/17 1:05 AM, Patrick Ohly wrote:
> > This fixes a potential pollution by the build host and build error
> > when yacc isn't installed on the build host:
> >
> > | ../../libtasn1-4.9/build-aux/ylwrap: line 175: yacc: command not found
> > | Makefile:1116: recipe for target 'ASN1.c' failed
> > | make[3]: *** [ASN1.c] Error 127
> >
> > Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
> > ---
> > meta/recipes-support/gnutls/libtasn1_4.9.bb | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/meta/recipes-support/gnutls/libtasn1_4.9.bb b/meta/recipes-support/gnutls/libtasn1_4.9.bb
> > index b8ff9eaf7a9..3da5d4bcc56 100644
> > --- a/meta/recipes-support/gnutls/libtasn1_4.9.bb
> > +++ b/meta/recipes-support/gnutls/libtasn1_4.9.bb
> > @@ -16,6 +16,8 @@ SRC_URI = "${GNU_MIRROR}/libtasn1/libtasn1-${PV}.tar.gz \
> > file://0004-tools-eliminated-compiler-warnings.patch \
> > "
> >
> > +DEPENDS = "bison-native"
> > +
>
> nit on style, you generally put checksum assignments immediately after
> SRC_URI containing the origninal src location. Secondly, if we use +=
> then we dont run the risk of it overwriting prior assignments if any
Makes sense, will change that as suggested.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
prev parent reply other threads:[~2017-02-02 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 9:05 [PATCH] libtasn1: depends on yacc Patrick Ohly
2017-02-01 16:56 ` Khem Raj
2017-02-02 11:20 ` Patrick Ohly [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=1486034426.14889.46.camel@intel.com \
--to=patrick.ohly@intel.com \
--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