From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: rongqing.li@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] mklibs-native: avoid failure on symbol provided by application
Date: Mon, 29 Jun 2015 08:05:44 +0100 [thread overview]
Message-ID: <1435561544.7287.10.camel@linuxfoundation.org> (raw)
In-Reply-To: <1435546323-11539-1-git-send-email-rongqing.li@windriver.com>
On Mon, 2015-06-29 at 10:52 +0800, rongqing.li@windriver.com wrote:
> From: Yuanjie Huang <yuanjie.huang@windriver.com>
>
> Undefined symbols in a library can be provided by the application
> that links to the library, such as `logsink' in libmultipath.so.0.
> This fix checks the type of object in which the symbol is needed
> and the existence of the symbol in application, when a symbol
> cannot be provided by libraries. It prevents false alarm on absence
> of symbols.
>
> Signed-off-by: Yuanjie Huang <yuanjie.huang@windriver.com>
> ---
> ...failure-on-symbol-provided-by-application.patch | 100 +++++++++++++++++++++
> .../mklibs/mklibs-native_0.1.40.bb | 1 +
> 2 files changed, 101 insertions(+)
> create mode 100644 meta/recipes-devtools/mklibs/files/avoid-failure-on-symbol-provided-by-application.patch
>
> diff --git a/meta/recipes-devtools/mklibs/files/avoid-failure-on-symbol-provided-by-application.patch b/meta/recipes-devtools/mklibs/files/avoid-failure-on-symbol-provided-by-application.patch
> new file mode 100644
> index 0000000..798212a
> --- /dev/null
> +++ b/meta/recipes-devtools/mklibs/files/avoid-failure-on-symbol-provided-by-application.patch
> @@ -0,0 +1,100 @@
> +From f172101130604e4a9efa5746f4d8d30de99a0fdc Mon Sep 17 00:00:00 2001
> +From: Yuanjie Huang <yuanjie.huang@windriver.com>
> +Date: Fri, 17 Apr 2015 14:48:20 +0800
> +Subject: [PATCH] avoid failure on symbol provided by application
> +
> +Undefined symbols in a library can be provided by the application
> +that links to the library, such as `logsink' in libmultipath.so.0.
> +This fix checks the type of object in which the symbol is needed
> +and the existence of the symbol in application, when a symbol
> +cannot be provided by libraries. It prevents false alarm on absence
> +of symbols.
> +
> +Signed-off-by: Yuanjie Huang <yuanjie.huang@windriver.com>
No Upstream-Status?
Cheers,
Richard
prev parent reply other threads:[~2015-06-29 7:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 2:52 [PATCH] mklibs-native: avoid failure on symbol provided by application rongqing.li
2015-06-29 7:05 ` Richard Purdie [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=1435561544.7287.10.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rongqing.li@windriver.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 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.