From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Chong Lu <Chong.Lu@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] flex: not to build shared libraries
Date: Wed, 05 Mar 2014 09:21:23 +0000 [thread overview]
Message-ID: <1394011283.31845.97.camel@ted> (raw)
In-Reply-To: <c00e7a2047ec6a4b4f46722f49176b08ded90509.1394010463.git.Chong.Lu@windriver.com>
On Wed, 2014-03-05 at 17:18 +0800, Chong Lu wrote:
> Some packages do not link successfully using shared libraries.
> When link something to libfl.so, we will get this:
>
> libfl.so: undefined reference to `yylex'
>
> So we only build static libraries to fix this issue.
>
> Signed-off-by: Chong Lu <Chong.Lu@windriver.com>
> ---
> .../files/flex-not-to-build-shared-libraries.patch | 39 ++++++++++++++++++++++
> meta/recipes-devtools/flex/flex.inc | 1 +
> 2 files changed, 40 insertions(+)
> create mode 100644 meta/recipes-devtools/flex/files/flex-not-to-build-shared-libraries.patch
Why aren't the shared libraries working? Which packages show this
problem? Is this not a problem in the recipes using the shared
libraries?
At the very least this patch needs more explanation but I don't like the
idea.
Cheers,
Richard
next prev parent reply other threads:[~2014-03-05 9:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 9:18 [PATCH 0/1] flex: not to build shared libraries Chong Lu
2014-03-05 9:18 ` [PATCH 1/1] " Chong Lu
2014-03-05 9:21 ` Richard Purdie [this message]
2014-03-05 9:58 ` Lu Chong
2014-03-05 11:37 ` Burton, Ross
2014-03-05 12:49 ` Paul Barker
2014-03-05 13:45 ` Paul Barker
2014-03-07 1:15 ` Paul Barker
2014-03-05 9:43 ` Burton, Ross
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=1394011283.31845.97.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=Chong.Lu@windriver.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 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.