Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Kevin Tian <kevin.tian@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: flex wrapper returns wrong version
Date: Thu, 9 May 2013 15:03:19 +0200	[thread overview]
Message-ID: <20130509130319.GE3188@jama> (raw)

[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]

Flex wrapper was added with:
commit d835488c526aa61163ade503c6586eaa59509a07
Author: Kevin Tian <kevin.tian@intel.com>
Date:   Wed Jan 5 10:26:36 2011 +0800

    flex-native: create a wrapper script for sstate installation

    flex-native encodes M4 staging path in its binary, which breaks sstate
    installation in a new build environment. Use create_wrapper to create
    a wrapper script which explicitly set M4 environmental variable to the
    new path

and --version returns `basename $0` --version, so in my case:
sysroots/x86_64-linux/usr/bin/flex --version
flex.real 2.5.35

Which isn't parsed correctly e.g. in newer webkit
|   Could NOT find FLEX: Found unsuitable version "flex.real 2.5.35", but
|   required is at least "2.5.34" (found
|   /OE/shr-core/tmp-eglibc/sysroots/x86_64-linux/usr/bin/flex)

we can probably work around it by changing regexp in
/sysroots/x86_64-linux/usr/share/cmake-2.8/Modules/FindFLEX.cmake

but it would be nice to fix it in flex.

Cheers,

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

             reply	other threads:[~2013-05-09 13:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-09 13:03 Martin Jansa [this message]
2013-05-09 14:31 ` [PATCH] flex: fix reported executable name caused by OE wrapper Martin Jansa
2013-05-09 17:55   ` Saul Wold
2013-05-10 10:21     ` [PATCHv2] " Martin Jansa

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=20130509130319.GE3188@jama \
    --to=martin.jansa@gmail.com \
    --cc=kevin.tian@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