From: Khem Raj <raj.khem@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] core-image-minimal-initramfs: add libgcc into the initramfs image
Date: Thu, 7 Mar 2019 06:45:30 -0800 [thread overview]
Message-ID: <CAMKF1sqoUULB=P9e6XLnGfxHBYM_ma+9Yfyv-yKqqSKHgZ0-sA@mail.gmail.com> (raw)
In-Reply-To: <CAJTo0LZCbH6XyQrWevL0g0f1OsCV3MmvcPme6Qf8VR17uUYVNA@mail.gmail.com>
On Thu, Mar 7, 2019 at 4:39 AM Burton, Ross <ross.burton@intel.com> wrote:
>
> On Thu, 7 Mar 2019 at 12:34, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > The customer needs to depend on libgcc in their app, or their
> > initramfs, we're not adding random dependencies to the initramfs "just
> > in case".
>
> Part of the goal of my ELF parser rewrite was to make it easy to add
> libgcc dependencies on binaries that use pthread_cancel automatically.
>
your suggestion about letting needing package rdep on it right, but
adding a hardcoded dependency on libgcc is not. We have to consider
a case where where there are alternatives to libgcc which can provide
same functionality and is preferred.
> Ross
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2019-03-07 14:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 6:51 [PATCH] core-image-minimal-initramfs: add libgcc into the initramfs image Zhixiong Chi
2019-03-07 9:05 ` Burton, Ross
2019-03-07 10:00 ` Zhixiong Chi
2019-03-07 12:33 ` Richard Purdie
2019-03-07 12:39 ` Burton, Ross
2019-03-07 14:45 ` Khem Raj [this message]
2019-03-07 14:47 ` 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='CAMKF1sqoUULB=P9e6XLnGfxHBYM_ma+9Yfyv-yKqqSKHgZ0-sA@mail.gmail.com' \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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.