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 in
On 3/8/18 4:10 PM, Marcelo E. Magallon wrote:
> On Thu, Mar 08, 2018 at 03:16:44PM -0600, Mark Hatle wrote:
>
>> RDEPENDS are automatically promoted to DEPENDS (build-time). I would
>> normally
>> expect libgcc_s.so.1 to be present via the typical default depends. Does
>> your
>> recipe have a
On Thu, Mar 08, 2018 at 01:30:28PM -0800, robert_jos...@selinc.com wrote:
In the case of btrfs-tools, it was simply that it needed libgcc_s.so.1 at
runtime on the target, which my patch fixed. For me, the image I was
building normally worked fine because some other package would pull in
libgcc,
On Thu, Mar 08, 2018 at 03:16:44PM -0600, Mark Hatle wrote:
RDEPENDS are automatically promoted to DEPENDS (build-time). I would normally
expect libgcc_s.so.1 to be present via the typical default depends. Does your
recipe have an INHIBIT_DEFAULT_DEPENDS (I think that is it?) defined? If so,
"Marcelo E. Magallon" wrote on 03/08/2018
01:00:28 PM:
> From: "Marcelo E. Magallon"
> To: ,
> Cc: "yocto@yoctoproject.org"
> Date: 03/08/2018 01:01 PM
> Subject: Re: [yocto] btrfs-tools Requires libgcc_s.so.1
>
> Sorry to go off on a tan
On 3/8/18 3:00 PM, Marcelo E. Magallon wrote:
> Sorry to go off on a tangent:
>
> On Fri, Mar 04, 2016 at 04:12:54PM -0800, robert_jos...@selinc.com wrote:
>
root@test:~# btrfs scrub start /
scrub started on /, fsid 79dc4fed-a0f7-43e2-b9e7-056b1a2c4cdd
>> (pid=333)
libgcc_s.so.1 mu
Sorry to go off on a tangent:
On Fri, Mar 04, 2016 at 04:12:54PM -0800, robert_jos...@selinc.com wrote:
> root@test:~# btrfs scrub start /
> scrub started on /, fsid 79dc4fed-a0f7-43e2-b9e7-056b1a2c4cdd
(pid=333)
> libgcc_s.so.1 must be installed for pthread_cancel to work
>
> I can solve thi
"Burton, Ross" wrote on 03/04/2016 04:17:53 PM:
> Would you be able to send that to the oe-core list (openembedded-
> c...@lists.openembedded.org) using git-send-email (ideally,
> attaching the output of git format-patch will do) to get your
> authorship transferred correctly? That's the formal
On 5 March 2016 at 00:12, wrote:
> What is the process for getting this fixed upstream? Trivial patch is
> below, if that is sufficient.
>
Would you be able to send that to the oe-core list (
openembedded-c...@lists.openembedded.org) using git-send-email (ideally,
attaching the output of git for
Khem Raj wrote on 03/04/2016 03:26:37 PM:
>
> On Sat, Mar 5, 2016 at 7:17 AM, wrote:
> > I'm building an image using btrfs and I noticed a problem with the
> > btrfs-tools recipe in Jethro (using core-image-minimal and a 64-bit
> > machine). The recipe builds fine, but I get the following error
On Sat, Mar 5, 2016 at 7:17 AM, wrote:
> I'm building an image using btrfs and I noticed a problem with the
> btrfs-tools recipe in Jethro (using core-image-minimal and a 64-bit
> machine). The recipe builds fine, but I get the following error when
> attempting certain operations using btrfs, suc
I'm building an image using btrfs and I noticed a problem with the
btrfs-tools recipe in Jethro (using core-image-minimal and a 64-bit
machine). The recipe builds fine, but I get the following error when
attempting certain operations using btrfs, such as trying to start a
scrub:
root@test:~# b
12 matches
Mail list logo