This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Basic requirements for supporting OS and machine ports.
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: Tulio Magno Quites Machado Filho <tuliom at linux dot vnet dot ibm dot com>, GNU C Library <libc-alpha at sourceware dot org>, Szabolcs Nagy <szabolcs dot nagy at arm dot com>, Richard Henderson <rth at redhat dot com>, Mike Frysinger <vapier at gentoo dot org>, Andreas Schwab <schwab at suse dot de>, Chris Metcalf <cmetcalf at mellanox dot com>, Chung-Lin Tang <chunglin_tang at mentor dot com>, Steven Munroe <sjmunroe at us dot ibm dot com>, Andreas Krebbel <krebbel at linux dot vnet dot ibm dot com>, David Miller <davem at davemloft dot net>, Siddhesh Poyarekar <siddhesh at gotplt dot org>, Florian Weimer <fweimer at redhat dot com>, Aurelien Jarno <aurelien at aurel32 dot net>, Adam Conrad <adconrad at 0c3 dot net>
- Date: Fri, 21 Apr 2017 16:52:20 +0000
- Subject: Re: Basic requirements for supporting OS and machine ports.
- Authentication-results: sourceware.org; auth=none
- References: <c501b05e-3ae1-5bc8-b5a7-b6c2dabb98bc@redhat.com> <alpine.DEB.2.20.1704191505450.28423@digraph.polyomino.org.uk> <87o9vs1dm6.fsf@totoro.br.ibm.com> <alpine.DEB.2.20.1704192139570.9217@digraph.polyomino.org.uk> <87lgqv16b5.fsf@totoro.br.ibm.com> <alpine.DEB.2.20.1704201605170.1490@digraph.polyomino.org.uk> <93baa56c-2927-04d6-570d-b63857235591@redhat.com>
On Fri, 21 Apr 2017, Carlos O'Donell wrote:
> So it sounds like you don't object to the basic requirements, just that
> supporting the basic requirements needs more infrastructure work.
>
> Could we then just agree on *one* basic requirement? That the machine
> and OS have build-many-glibcs.py support?
I don't object to a requirement of the form: new (machine, OS, ABI)
configurations are expected to have such support contributed when the
configuration support is added, and without such support there is no
expectation that developers will help fix any build or build-time-test
problems their patches may cause on the configurations lacking such
support.
This does not impose an ordering in which people must get support for
their (machine, OS, ABI) into various toolchain / kernel components, but
if e.g. the glibc support goes in before the kernel support, the build
with build-many-glibcs.py won't actually work and so there is no
expectation of people fixing build problems until all the relevant support
is upstream.
--
Joseph S. Myers
joseph@codesourcery.com