From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-74879-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 87723 invoked by alias); 17 Nov 2016 16:52:38 -0000
Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <libc-alpha.sourceware.org>
List-Subscribe: <mailto:libc-alpha-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/libc-alpha/>
List-Post: <mailto:libc-alpha@sourceware.org>
List-Help: <mailto:libc-alpha-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: libc-alpha-owner@sourceware.org
Received: (qmail 87709 invoked by uid 89); 17 Nov 2016 16:52:37 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=ham version=3.3.2 spammy=3.5, Hx-languages-length:824, wish
X-HELO: mail-qt0-f176.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:subject:to:references:from:message-id:date
         :user-agent:mime-version:in-reply-to:content-transfer-encoding;
        bh=HLdIoz87VlkUB2iUO1JyT0C5GYDP6pZGQG4nSlqEzik=;
        b=iC2aRbiUCYz56nckzsw2J0dRPgf268urEoZr9mYq+OAv6jCnE/w+vrDmVe3kpVpY8v
         n8uT/xNk3lVwc+OkQOMS/XyK87v9TFr5EWCB8taJcSuglO437lJMWhFv26UH0NRrEGCY
         GHkK9pvxTroIdHA5jR4XfhFNL9f7oR0EO3zG+qLOdSmWOGiI7jVwnc21aXxHgI6aTttT
         byjlcbw+vZQ66TvLrB2tGto1iMFytN/QvwSsSWAwnftF/O2MkM2wg04LqLkmqGykNsSW
         TytKnM9UMYQxNRxmf392WqSy7YLjXrc2v+jpvBeGhIt7TrZvNBnMpgUA+Y4MMYQD0yPW
         JzxQ==
X-Gm-Message-State: AKaTC03On3LIaYy3sNpxOLQ5LnTfBtk7FPgLBuYNIOkwV3gfC92SmI9i2nRPlOcCGxAeJQ==
X-Received: by 10.237.34.152 with SMTP id p24mr3058748qtc.45.1479401545673;
        Thu, 17 Nov 2016 08:52:25 -0800 (PST)
Subject: Re: Add script to build many glibc configurations
To: libc-alpha@sourceware.org
References: <alpine.DEB.2.20.1611091625430.7263@digraph.polyomino.org.uk>
From: Zack Weinberg <zackw@panix.com>
Message-ID: <dcc3fd8e-0865-af11-a998-10fbea75009c@panix.com>
Date: Thu, 17 Nov 2016 16:52:00 -0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Icedove/45.4.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.20.1611091625430.7263@digraph.polyomino.org.uk>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-SW-Source: 2016-11/txt/msg00632.txt.bz2

On 11/09/2016 11:27 AM, Joseph Myers wrote:
> This patch adds a Python (3.5 or later) script to build many different
> configurations of glibc, including building the required cross
> compilers first.  It's not intended to change any patch testing
> requirements, although some people may wish to use it for high-risk
> patches such as adding warning options ...

Since this does its own glibc checkout, it's not clear to me how one
should use it to test a patch(set).  I presume that whatever one does,
it only affects the "glibcs" step, but what actually do you do?  Do you
manually update /some/where/src/glibc to contain the code you want
tested and then run "glibcs", or do you somehow tell
build-many-glibcs.py the name of a branch you want tested, or what?

Thanks,
zw