Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [External] [PATCH] core/pkg-generic: fix instrumentation for packages that install nowhere
Date: Wed, 16 Jun 2021 21:59:02 +0200	[thread overview]
Message-ID: <20210616195902.GR2610983@scaer> (raw)
In-Reply-To: <DM2P110MB0105D1560BC1E8EC48F2F8AAF2309@DM2P110MB0105.NAMP110.PROD.OUTLOOK.COM>

Matthew, All,

On 2021-06-15 19:40 +0000, Weber, Matthew L                            Collins spake thusly:
> > 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

Applied to master, thanks.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2021-06-16 19:59 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 ` [Buildroot] [External] " Weber, Matthew L Collins
2021-06-16 19:59   ` Yann E. MORIN [this message]
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=20210616195902.GR2610983@scaer \
    --to=yann.morin.1998@free.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox