This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Add script to build many glibc configurations

On Thu, 17 Nov 2016, Zack Weinberg wrote:

> 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
> the name of a branch you want tested, or what?

You patch the script's glibc checkout (or switch it to a different branch, 
or whatever) at some point after the checkout step and before running the 
"glibcs" build.  (The model is that if you're often running tests for many 
configurations, you do the host-libraries and compilers steps once, with 
some stable GCC version, and then can keep using the previously built 
compilers when running the "glibcs" step with new and possibly patched 
glibc - so saving time compared to rebuilding the compilers from scratch 
every time.)

(The checkout step will not notice if you've manually patched or changed 
the branch of a checkout, and will fail if git pull fails, e.g. if it 
tries to update a file where you have local changes.)

Joseph S. Myers

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]