public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: "Maciej W. Rozycki" <macro@wdc.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, Jeffrey Law <law@redhat.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	Julian Brown <julian@codesourcery.com>,
	Tobias Burnus <tobias@codesourcery.com>,
	Thomas Schwinge <thomas@codesourcery.com>,
	Chung-Lin Tang <cltang@codesourcery.com>,
	Ian Lance Taylor <iant@golang.org>,
	libffi-discuss@sourceware.org
Subject: Re: [PATCH v3 2/4] libffi/test: Fix compilation for build sysroot
Date: Mon, 30 Mar 2020 11:45:46 -0700	[thread overview]
Message-ID: <7A59EACC-C414-4278-8BEC-F0D02792E62F@comcast.net> (raw)
In-Reply-To: <alpine.LFD.2.21.2003251555240.24019@redsun52.ssa.fujisawa.hgst.com>

On Mar 26, 2020, at 3:00 PM, Maciej W. Rozycki <macro@wdc.com> wrote:
> 
> I have actually considered extracting the bits already, but I hesitated 
> putting that forward that as having looked at the part that we require I 
> have thought it to be very messy:

Yeah, sometimes it's like that.  I glanced at the work, if you think it's a step forward, I'd support importing it, my take, import from upstream isn't a bad way to go.

> So I am in favour of retaining the mechanism rather than using my earlier 
> proposal, however I'm in two minds as to how to proceed.  Integrating the 
> change as it is will make us having clutter left in the tree after `make 
> distclean', but we can do it right away.

I'd support this.  distclean is one rm -rf away from being clean enough.  I'd not let that gate or hold up the import.

If there is work that we want that's more to do with in tree building and testing (sys root fun, multilibs), while not ideal, we can deviate from upstream to support that.  Though, if there is a way to naturally support that, that upstream can accept, that'd be better.

  reply	other threads:[~2020-03-30 18:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LFD.2.21.2002271413200.18621@redsun52.ssa.fujisawa.hgst.com>
     [not found] ` <alpine.LFD.2.21.2002272337550.18621@redsun52.ssa.fujisawa.hgst.com>
     [not found]   ` <CAMe9rOqt8pLyDus=hr6FXkBCi5M_HE-a41-MTX2Loy4JedQPww@mail.gmail.com>
     [not found]     ` <alpine.LFD.2.21.2002281331290.18621@redsun52.ssa.fujisawa.hgst.com>
     [not found]       ` <CAMe9rOoyrWh_ALBYxViEwUXJmJZXyg+mc=zQ3zQd2g-Tub8_pA@mail.gmail.com>
     [not found]         ` <bb19d498a240ed4f892bc5ebec5719474c0ea1f8.camel@redhat.com>
     [not found]           ` <CAMe9rOraaSgB7R3rr-QH4dD2+OED7=0MDuLMQX-caY0FrBj_4A@mail.gmail.com>
     [not found]             ` <alpine.LFD.2.21.2003172147281.24019@redsun52.ssa.fujisawa.hgst.com>
     [not found]               ` <805572B0-892A-4811-8CB3-762023C8703F@comcast.net>
2020-03-26 22:00                 ` Maciej W. Rozycki
2020-03-30 18:45                   ` Mike Stump [this message]
2020-03-31 21:11                     ` Maciej W. Rozycki

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=7A59EACC-C414-4278-8BEC-F0D02792E62F@comcast.net \
    --to=mikestump@comcast.net \
    --cc=cltang@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=iant@golang.org \
    --cc=julian@codesourcery.com \
    --cc=law@redhat.com \
    --cc=libffi-discuss@sourceware.org \
    --cc=macro@wdc.com \
    --cc=thomas@codesourcery.com \
    --cc=tobias@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).