From: Phil Blundell <pb@pbcl.net>
To: Khem Raj <raj.khem@gmail.com>
Cc: richard.purdie@intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libgcc.inc: package baremetal multilib libraries
Date: Mon, 14 Sep 2015 20:53:17 +0100 [thread overview]
Message-ID: <1442260397.2948.87.camel@pbcl.net> (raw)
In-Reply-To: <7D6F58E5-BF37-4757-8B9A-5C37BAE5ED8E@gmail.com>
On Mon, 2015-09-14 at 09:38 -0700, Khem Raj wrote:
> > On Sep 14, 2015, at 9:22 AM, Juro Bystricky <juro.bystricky@intel.com> wrote:
> >
> > When building libgcc for baremetal cross-compilers, some files and libraries
> > may be built but not packaged. This patch fixes errors such as these:
> >
> > ERROR: QA Issue: libgcc: Files/directories were installed but not shipped in any package:
> > /usr/lib/arm-poky-eabi/4.9.3/thumb
> > /usr/lib/arm-poky-eabi/4.9.3/fpu
> > /usr/lib/arm-poky-eabi/4.9.3/thumb/libgcov.a
> > /usr/lib/arm-poky-eabi/4.9.3/thumb/crtn.o
> > /usr/lib/arm-poky-eabi/4.9.3/thumb/crtend.o
> > /usr/lib/arm-poky-eabi/4.9.3/thumb/crtbegin.o
> > /usr/lib/arm-poky-eabi/4.9.3/thumb/libgcc.a
> > /usr/lib/arm-poky-eabi/4.9.3/thumb/crti.o
> > /usr/lib/arm-poky-eabi/4.9.3/fpu/libgcov.a
> > /usr/lib/arm-poky-eabi/4.9.3/fpu/crtn.o
> > /usr/lib/arm-poky-eabi/4.9.3/fpu/crtend.o
> > /usr/lib/arm-poky-eabi/4.9.3/fpu/crtbegin.o
> > /usr/lib/arm-poky-eabi/4.9.3/fpu/libgcc.a
> > /usr/lib/arm-poky-eabi/4.9.3/fpu/crti.o
> > Please set FILES such that these items are packaged. Alternatively if they are unneeded,
> > avoid installing them or delete them within do_install. [installed-vs-shipped]
> >
> > Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
> > ---
> > meta/recipes-devtools/gcc/libgcc.inc | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/meta/recipes-devtools/gcc/libgcc.inc b/meta/recipes-devtools/gcc/libgcc.inc
> > index 739adbd..95709e4 100644
> > --- a/meta/recipes-devtools/gcc/libgcc.inc
> > +++ b/meta/recipes-devtools/gcc/libgcc.inc
> > @@ -28,6 +28,12 @@ FILES_${PN}-dev = "\
> > ${libdir}/${TARGET_SYS}/${BINV}/libgcov.a \
> > "
> >
> > +FILES_${PN}-dev_libc-baremetal = "\
> > + ${base_libdir}/ \
> > + ${libdir}/* \
> > + ${libdir}/${TARGET_SYS}/* \
> > +”
>
> why not put it into libgcc-dev itself
Agreed. I think the real issue here is nothing really to do with
baremetal, it's just that the existing FILES_${PN}-dev pattern doesn't
consider multilib for anything other than IA and mips.
p.
next prev parent reply other threads:[~2015-09-14 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 16:22 [PATCH] libgcc.inc: package baremetal multilib libraries Juro Bystricky
2015-09-14 16:38 ` Khem Raj
2015-09-14 19:53 ` Phil Blundell [this message]
2015-09-15 16:23 ` Bystricky, Juro
2015-09-21 23:21 ` [PATCH v2 0/1] libgcc: package multiple libraries Juro Bystricky
2015-09-21 23:21 ` [PATCH v2] libgcc.inc: package baremetal multilib libraries Juro Bystricky
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=1442260397.2948.87.camel@pbcl.net \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox