Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH] mrouted-3.9.4: intitial recipe
Date: Fri, 4 Mar 2011 11:51:35 -0700	[thread overview]
Message-ID: <4D7134B7.7070209@mentor.com> (raw)
In-Reply-To: <4D7122B1.3080609@opendreambox.org>

On 03/04/2011 10:34 AM, Andreas Oberritter wrote:
> On 03/04/2011 05:14 PM, Paul Menzel wrote:
>> Am Freitag, den 04.03.2011, 07:40 -0800 schrieb Khem Raj:
>>> On 3/4/2011 5:12 AM, Andreas Oberritter wrote:
>>>> Signed-off-by: Andreas Oberritter<obi@opendreambox.org>
>>>> ---
>>>> This was only compile-tested. It would be nice to get some feedback.
>>>
>>> Looks ok to me. Does it need any deps? May be building it from scratch
>>> will detect it if not otherwise
>>>
>>> Acked-by: Khem Raj<raj.khem@gmail.com>
>>
>> With the dependencies addressed and …
>
> Other than using bison, there are no dependencies that I know of.
> Binutils already depends on bison, so it's always available to cross
> recipes. Should it be mentioned in mrouted explicitly, or is this a case
> like binutils, gcc and libc, which never need to be mentioned in DEPENDS?

You should always spell out bison-native and flex-native.

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2011-03-04 18:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04  3:27 Ask for a bb.file of mrouted-3.9.4.tar.gz wyang
2011-03-04 13:12 ` [PATCH] mrouted-3.9.4: intitial recipe Andreas Oberritter
2011-03-04 15:40   ` Khem Raj
2011-03-04 16:14     ` Paul Menzel
2011-03-04 17:34       ` Andreas Oberritter
2011-03-04 18:51         ` Tom Rini [this message]
2011-03-04 20:34         ` Phil Blundell
2011-03-04 18:45       ` Tom Rini
2011-03-04 21:11         ` Andreas Oberritter

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=4D7134B7.7070209@mentor.com \
    --to=tom_rini@mentor.com \
    --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