From: Patrick Ohly <patrick.ohly@intel.com>
To: Mark Hatle <mark.hatle@windriver.com>,
"Marcelo E. Magallon" <marcelo.magallon@hpe.com>
Cc: yocto@yoctoproject.org
Subject: Re: btrfs-tools Requires libgcc_s.so.1
Date: Fri, 09 Mar 2018 08:56:32 +0100 [thread overview]
Message-ID: <1520582192.7229.1.camel@intel.com> (raw)
In-Reply-To: <d6e0c216-5c38-0fb1-d8fb-df6aa33acfff@windriver.com>
On Thu, 2018-03-08 at 19:18 -0600, Mark Hatle wrote:
> Yes, the dlopen means the automated processing can't identify the
> need.. and
> then the RDEPEND is the correct solution.
>
> (This might be a reasonable bug/enhancement request to the
> system. Look for
> pthread_cancel and automatically infer that libgcc is required.)
There is already a feature request for that:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10954
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2018-03-09 7:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 23:17 btrfs-tools Requires libgcc_s.so.1 robert_joslyn
2016-03-04 23:26 ` Khem Raj
2016-03-05 0:12 ` robert_joslyn
2016-03-05 0:17 ` Burton, Ross
2016-03-05 0:54 ` [PATCH] btrfs-tools: Add libgcc to RDEPENDS robert_joslyn
2016-03-05 1:17 ` btrfs-tools Requires libgcc_s.so.1 robert_joslyn
2018-03-08 21:00 ` Marcelo E. Magallon
2018-03-08 21:16 ` Mark Hatle
2018-03-08 22:10 ` Marcelo E. Magallon
2018-03-09 1:18 ` Mark Hatle
2018-03-09 7:56 ` Patrick Ohly [this message]
2018-03-08 21:30 ` robert_joslyn
2018-03-08 22:25 ` Marcelo E. Magallon
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=1520582192.7229.1.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=marcelo.magallon@hpe.com \
--cc=mark.hatle@windriver.com \
--cc=yocto@yoctoproject.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.