From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 36228 invoked by alias); 19 Jan 2018 15:12:00 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 36170 invoked by uid 89); 19 Jan 2018 15:11:59 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy= X-HELO: relay1.mentorg.com Date: Fri, 19 Jan 2018 15:12:00 -0000 From: Joseph Myers To: Thomas Schwinge CC: Florian Weimer , GNU C Library , , Samuel Thibault , David Michael Subject: Re: Upstreaming the glibc Hurd port In-Reply-To: <877eseuefd.fsf@euler.schwinge.homeip.net> Message-ID: References: <20180118124537.yampmyfjsbi6wvia@var.youpi.perso.aquilenet.fr> <20180118135758.xqla2yevcrjjk7si@var.youpi.perso.aquilenet.fr> <87mv1btffy.fsf@hertz.schwinge.homeip.net> <20180118151446.zqlmpbmgg4kvs2y3@var.youpi.perso.aquilenet.fr> <20180118154251.ynfyugkmog7kujom@var.youpi.perso.aquilenet.fr> <20180118165923.ymreisuzexxz4gt3@var.youpi.perso.aquilenet.fr> <20180118235924.r4z4ppvj7xlvmmfp@var.youpi.perso.aquilenet.fr> <87a7xaupjx.fsf@euler.schwinge.homeip.net> <877eseuefd.fsf@euler.schwinge.homeip.net> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-SW-Source: 2018-01/txt/msg00659.txt.bz2 On Fri, 19 Jan 2018, Thomas Schwinge wrote: > Hi! > > On Fri, 19 Jan 2018 13:08:01 +0000, Joseph Myers wrote: > > On Fri, 19 Jan 2018, Thomas Schwinge wrote: > > > > [build-many-glibcs.py] > > > Do you have advice on versions to use of mig / gnumach / hurd? > > > > Currently, build-many-glibcs.py uses (by default) release versions of most > > components other than glibc itself, release branches for gcc / binutils. > > Should the most recent releases from ftp.gnu.org of mig / gnumach / hurd > > be used for building current glibc for Hurd, or is it preferable or > > necessary to use newer development versions of those components? > > The current releases should generally be fine, yes. The source file sysdeps/mach/hurd/bits/errno.h is generated from sources including some headers from those components. I don't know how often those may change in ways that affect that header, or what versions the current header corresponds to, but in any case it's a known issue that there are several generated files in the source tree that build-many-glibcs.py doesn't yet touch on checkout. > (This reminds me that I wanted to publish new GNU Mach, MIG, Hurd, > libpthread releases, but no need for you to wait for these, as far as I > know.) Regarding libpthread, I don't propose build-many-glibcs.py support for a separate libpthread component; what's relevant is whatever version goes on the sthibaul/hurd-builds branch of glibc (set up to build without the old add-ons mechanism), and in due course on master. -- Joseph S. Myers joseph@codesourcery.com