From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 56383 invoked by alias); 21 Jan 2020 05:07:30 -0000 Mailing-List: contact libffi-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libffi-discuss-owner@sourceware.org Received: (qmail 56361 invoked by uid 89); 21 Jan 2020 05:07:29 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=H*RU:209.85.208.68, HX-Spam-Relays-External:209.85.208.68 X-HELO: mail-ed1-f68.google.com Received: from mail-ed1-f68.google.com (HELO mail-ed1-f68.google.com) (209.85.208.68) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 21 Jan 2020 05:05:46 +0000 Received: by mail-ed1-f68.google.com with SMTP id i16so1726173edr.5 for ; Mon, 20 Jan 2020 21:05:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=golang-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jRyXMS8qkIThD61bTDwXKRGVfxqt8sGFW59wweM2rj4=; b=lSBuQr45wxS8swNy0wVoAkEvmqBxjRhyOCud3QARPsuG+g/B0JKbDPZnO0YnQIqIXy Y42y0uJyVtGi94sT6cEmJRXObstgbxG64pYOTVbVaSGq9THrHpB9PbJc1dXQrESLPXjf KR+3raN5LXAfn17oo32gRjjwVTsRsaQiOy0DqmaLoA2TzcfQUxiK7tPT0nFlOEOcjAfr LqY7DlvHCG4VpEvmJHR0U0H5oqoRAhzsyaR6S7KSZpZ/73ybeMelaMRBbYJFs95JUm59 yjAzas3xI9SEyputl1SNpCJ+v0QO7s9yR8Ant3Ek7BUVgRnVAJ4qFuV+npwnG2uSlLKJ WIvg== MIME-Version: 1.0 References: In-Reply-To: From: Ian Lance Taylor Date: Tue, 21 Jan 2020 05:07:00 -0000 Message-ID: Subject: Re: [PATCH v3] Add `--with-toolexeclibdir=' configuration option To: "Maciej W. Rozycki" Cc: Joseph Myers , gcc-patches , libffi-discuss@sourceware.org, gofrontend-dev , zlib@gzip.org Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2020/txt/msg00003.txt On Mon, Jan 20, 2020 at 6:46 PM Maciej W. Rozycki wrote: > > Ian: Can we please coordinate this somehow? The libgo/ part, like all, > relies on config/toolexeclibdir.m4, so I can either: > > 1. push the whole change all at once and you'll push the libgo/ part to > your repo independently, which shouldn't be an issue except perhaps for > policy reasons as the changes will be identical anyway, or > > 2. push all the bits sans the libgo/ part and you'll push the libgo/ part > to your repo and then you'll merge it to GCC. > > There is a slight technical advantage to going with #1 as there'll be no > window where the new option is not consistently supported; it's also less > work as you won't have to do the merge. But I have no strong preference > either way. I'd rather do #2. Thanks. A small window is unlikely to matter to anyone. Let me know when the rest of the patch is committed. Ian