From: Martin Galvan <omgalvan.86@gmail.com>
To: libc-alpha@sourceware.org, siddhesh@sourceware.org,
joseph@codesourcery.com
Subject: Re: [PATCH v11] Add pretty printers for the NPTL lock types
Date: Thu, 08 Dec 2016 21:01:00 -0000 [thread overview]
Message-ID: <20161208210113.6291-1-omgalvan.86@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1612081855170.9769@digraph.polyomino.org.uk>
On Thu, Dec 8, 2016 at 18:56, Joseph Myers wrote:
> After a build and test run I see files scripts/test_printers_common.pyc
> and scripts/test_printers_exceptions.pyc created in the source directory.
> We'd like to be able to build with read-only source directories, could the
> tests be fixed not to create .pyc files (e.g. use python -B) or to create
> them in the build directory?
Sure, feel free to do so. I believe you could achieve that by setting PYTHON to 'python -B' in Rules, or maybe defining a separate PYTHONFLAGS variable.
I'd love to do it myself but I don't have access to a testing machine right now. It's a small change though, so it shouldn't be an issue.
next prev parent reply other threads:[~2016-12-08 21:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 3:04 Martin Galvan
2016-11-28 12:11 ` Stefan Liebler
2016-11-28 16:00 ` Martin Galvan
2016-12-04 12:41 ` Siddhesh Poyarekar
2016-12-04 20:56 ` Martin Galvan
2016-12-08 13:36 ` Siddhesh Poyarekar
2016-12-08 18:56 ` Joseph Myers
2016-12-08 21:01 ` Martin Galvan [this message]
2016-12-12 20:55 ` Martin Galvan
2016-12-12 23:15 ` Joseph Myers
2016-12-12 23:21 ` Martin Galvan
2016-12-14 18:20 ` Joseph Myers
2016-12-14 19:46 ` Martin Galvan
2016-12-17 18:10 ` Martin Galvan
2016-12-17 19:07 ` Siddhesh Poyarekar
2016-12-17 19:09 ` Martin Galvan
2016-12-22 16:35 ` Torvald Riegel
2016-12-22 16:44 ` Martin Galvan
2016-12-22 22:50 ` Torvald Riegel
2016-12-22 23:40 ` Martin Galvan
2016-12-23 17:05 ` Torvald Riegel
2016-12-23 17:40 ` Martin Galvan
2016-12-23 18:05 ` Martin Galvan
2016-12-23 18:48 ` Torvald Riegel
2016-12-23 19:38 ` Martin Galvan
2016-12-26 14:17 ` Martin Galvan
2017-01-02 12:48 ` Martin Galvan
2017-01-02 13:51 ` Joseph Myers
2017-01-02 14:35 ` Martin Galvan
2017-01-02 15:47 ` Torvald Riegel
2017-01-02 21:51 ` Joseph Myers
2017-01-03 7:27 ` Siddhesh Poyarekar
2017-01-06 21:58 ` Torvald Riegel
2017-01-09 19:37 ` Martin Galvan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161208210113.6291-1-omgalvan.86@gmail.com \
--to=omgalvan.86@gmail.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).