From: Weber, Matthew L Collins <Matthew.Weber@collins.com>
To: buildroot@busybox.net
Subject: [Buildroot] [External] [PATCH] core/pkg-generic: fix instrumentation for packages that install nowhere
Date: Tue, 15 Jun 2021 19:40:32 +0000 [thread overview]
Message-ID: <DM2P110MB0105D1560BC1E8EC48F2F8AAF2309@DM2P110MB0105.NAMP110.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20210613143207.2445691-1-yann.morin.1998@free.fr>
Yann,
> From: Yann E. MORIN <yann.morin.1998@gmail.com> on behalf of Yann E. MORIN <yann.morin.1998@free.fr>
> Sent: Sunday, June 13, 2021 9:32 AM
> To: buildroot at buildroot.org <buildroot@buildroot.org>
> Cc: Yann E. MORIN <yann.morin.1998@free.fr>; Weber, Matthew L Collins <Matthew.Weber@collins.com>; Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Subject: [External] [PATCH] core/pkg-generic: fix instrumentation for packages that install nowhere
> ?
> A (target [0]) package can independently declare installing in various
> locations: target, staging, or images. The default is to only install
> in target.
>
[snip]
>
> Fixes: #13836
>
> [0] a host package can't opt out of installing anything.
> [1] that one is actually missing AUFS_INSTALL_TARGET = NO, so this
> ??? hides the issue.
> [2] even us are not 100% clean on that topic: gcc will install files in
> ??? staging and target as part of the same step (not the build, granted,
> ??? but still...)
>
> Reported-by: "Weber, Matthew L Collins" <Matthew.Weber@collins.com>
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Tested-by: Matthew Weber <matthew.weber@collins.com
next prev parent reply other threads:[~2021-06-15 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 14:32 [Buildroot] [PATCH] core/pkg-generic: fix instrumentation for packages that install nowhere Yann E. MORIN
2021-06-15 19:40 ` Weber, Matthew L Collins [this message]
2021-06-16 19:59 ` [Buildroot] [External] " Yann E. MORIN
2021-06-21 20:18 ` [Buildroot] " Peter Korsgaard
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=DM2P110MB0105D1560BC1E8EC48F2F8AAF2309@DM2P110MB0105.NAMP110.PROD.OUTLOOK.COM \
--to=matthew.weber@collins.com \
--cc=buildroot@busybox.net \
/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.