All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: Matt Madison <matt@madison.systems>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] go-runtime: prevent host leakage into target objects
Date: Fri, 29 Sep 2017 11:27:19 -0300	[thread overview]
Message-ID: <CAP9ODKqrAFnbS2RqQSxSB9gX4Ban5sDjof4SjMw_yc7aEqZrpQ@mail.gmail.com> (raw)
In-Reply-To: <1506694551-4487-1-git-send-email-matt@madison.systems>

On Fri, Sep 29, 2017 at 11:15 AM, Matt Madison <matt@madison.systems> wrote:
> When building for a target whose architecture matches
> the build host's, the second pass through make.bash
> to build the shareable runtime would also overwrite
> the target's static cgo library with host-compatibile
> binaries.
>
> Fix this by running the host-side build once and
> target-only passes of make.bash twice, for static
> and shareable.  This ensures that what gets installed
> is target-compatible.
>
> [YOCTO #12136]
>
> Signed-off-by: Matt Madison <matt@madison.systems>

Acked-by: Otavio Salvador <otavio@ossystems.com.br>

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


  reply	other threads:[~2017-09-29 14:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-29 14:15 [PATCH] go-runtime: prevent host leakage into target objects Matt Madison
2017-09-29 14:27 ` Otavio Salvador [this message]
2017-10-03 22:02 ` Wold, Saul
2017-10-04 11:18   ` Matt Madison
2017-10-03 22:07 ` Saul Wold

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=CAP9ODKqrAFnbS2RqQSxSB9gX4Ban5sDjof4SjMw_yc7aEqZrpQ@mail.gmail.com \
    --to=otavio.salvador@ossystems.com.br \
    --cc=matt@madison.systems \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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.