public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Marinescu, Bogdan A" <bogdan.a.marinescu@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] flex: updated to 2.5.37
Date: Fri, 01 Feb 2013 14:56:20 +0000	[thread overview]
Message-ID: <1359730580.14071.64.camel@ted> (raw)
In-Reply-To: <CAMZjud1kH9o5iv+LU2QtaeSebftwXp+-vLF-ztSyxAOwktC8WA@mail.gmail.com>

On Fri, 2013-02-01 at 12:29 +0200, Marinescu, Bogdan A wrote:
> On Thu, Jan 31, 2013 at 6:30 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>         On Thu, 2013-01-31 at 13:53 +0200, Bogdan Marinescu wrote:
>         > Removed the patches to flex, because they are now applied to
>         the
>         > latest version.
>         >
>         > Signed-off-by: Bogdan Marinescu
>         <bogdan.a.marinescu@intel.com>
>         > ---
>         >  .../flex/flex/avoid-FORTIFY-warnings.patch         |   59
>         --------------------
>         >  .../flex/int-is-not-the-same-size-as-size_t.patch  |   42
>         --------------
>         >  meta/recipes-devtools/flex/flex_2.5.35.bb          |   11
>         ----
>         >  meta/recipes-devtools/flex/flex_2.5.37.bb          |    8
>         +++
>         >  4 files changed, 8 insertions(+), 112 deletions(-)
>         >  delete mode 100644
>         meta/recipes-devtools/flex/flex/avoid-FORTIFY-warnings.patch
>         >  delete mode 100644
>         meta/recipes-devtools/flex/flex/int-is-not-the-same-size-as-size_t.patch
>         >  delete mode 100644
>         meta/recipes-devtools/flex/flex_2.5.35.bb
>         >  create mode 100644
>         meta/recipes-devtools/flex/flex_2.5.37.bb
>         
>         
>         This failed to build for me:
> 
> 
> What image are you building? I am unable to reproduce this problem
> locally.
> 

It doesn't matter, "bitbake flex-native" fails.

It probably depends on what doc tools you have installed locally.

Cheers,

Richard





  reply	other threads:[~2013-02-01 15:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 11:53 [PATCH] flex: updated to 2.5.37 Bogdan Marinescu
2013-01-31 16:30 ` Richard Purdie
2013-02-01 10:29   ` Marinescu, Bogdan A
2013-02-01 14:56     ` Richard Purdie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-05-10 10:15 Bogdan Marinescu
2013-05-10 10:13 ` Marinescu, Bogdan A
2013-05-10 10:20 ` Martin Jansa
2013-05-10 10:32   ` Richard Purdie
2013-05-10 10:37     ` Martin Jansa
2013-05-10 10:46     ` Phil Blundell
2013-05-10 10:50       ` Phil Blundell
2013-05-10 11:00         ` Burton, Ross
2013-05-12  7:32           ` Richard Purdie
2013-05-27  7:48             ` Marinescu, Bogdan A

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=1359730580.14071.64.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bogdan.a.marinescu@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox