[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Changes by Donald Stufft : -- pull_requests: +914 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin Panter added the comment: Just to clarify, the current status is that the revision that Koobs identified is still in place, meaning that the AST files are regenerated into the build tree, not the source tree. I don’t think there is much else to do for this bug, unless Koobs can provide

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Roundup Robot added the comment: New changeset 36550e4f9b4c by Martin Panter in branch '3.5': Issue #15819: Remove old unconditional -IInclude option https://hg.python.org/cpython/rev/36550e4f9b4c New changeset a90daae58323 by Martin Panter in branch '3.6': Issue #15819: Merge include search fro

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Roundup Robot added the comment: New changeset 9cabcb4411ac by Martin Panter in branch '2.7': Issue #15819: Drop dead code; -IInclude already added unconditionally https://hg.python.org/cpython/rev/9cabcb4411ac -- ___ Python tracker

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Changes by Petri Lehtinen : -- nosy: -petri.lehtinen ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Kubilay Kocak added the comment: @Martin tldr; That was three years ago so I don't know if the issue remains. Perhaps a new out of tree builder will help answer that question. We(FreeBSD) gave up^W switched away from out of tree builds due to lack of support getting issues fixed and the freque

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin Panter added the comment: Matthias seems to have already applied his patch in Python 3.3 and 3.4+: revision f2cc3d8b88bb. Roumen: Is your problem still relevant? If so, perhaps open a separate bug to elaborate. Koobs: Is your problem with finding Python/Python-ast.c still relevant? Is

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin Panter added the comment: I’m not sure what the overall status of this bug is, so I will leave the versions as they are. Are the three comments from 2013 relevant, and is there anything I can do to help? The Python 2 code already unconditionally adds -IInclude (see Issue 786737), and d

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Kubilay Kocak added the comment: @Martin Maybe Zach (nosey'd) can help us get an out-of-tree builder set up? If this is relevant for 3.5+, versions should be updated accordingly. -- nosy: +zach.ware ___ Python tracker

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin Panter added the comment: Perhaps there should be a comment explaining that you can’t write to $(srcdir). Or even a buildbot that does an out-of-tree build. Every now and then I seem to be defending against patches that want to change targets back to $(srcdir). Also, Trent’s last change

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Changes by Gregory P. Smith : -- nosy: +gregory.p.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

koobs added the comment: I'm not sure how I missed this, but our FreeBSD ports that build out-of-tree required adding a local patchthat reverts the Makefile.pre.in change in ab6ab44921b2 when we updated each port to the latest releases of 2.7, 3.2 and 3.3: https://svnweb.freebsd.org/ports?vie

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Roumen Petrov added the comment: To update .hgtouch is not enough. Grammar, AST and importlib should left in source tree as before. -- nosy: +rpetrov ___ Python tracker ___ _

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Matthias Klose added the comment: just saw the comment about .hgtouch in http://bugs.python.org/issue15819#msg169484 attaching a patch for it here (as proposed on python-committers). -- nosy: +doko Added file: http://bugs.python.org/file28874/hgtouch.diff _

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Roundup Robot added the comment: New changeset 7e879a453bb3 by Trent Nelson in branch '2.7': Issue #15819: use standard autoconf preset output variables. http://hg.python.org/cpython/rev/7e879a453bb3 New changeset 65b3c41052b6 by Trent Nelson in branch '3.2': Issue #15819: use standard autoconf

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Roundup Robot added the comment: New changeset c35db4960d1c by Trent Nelson in branch '2.7': Issue #15819: tweak logic in previous commit (e0a2b14a3cf9). http://hg.python.org/cpython/rev/c35db4960d1c New changeset 5707c8a36cc0 by Trent Nelson in branch '3.2': Issue #15819: tweak logic in previou

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Trent Nelson added the comment: Things should be looking a lot better now across the board. I just committed fixes where appropriate to 2.7, 3.2, 3.3 and 3.x for this issue and two related issues: http://bugs.python.org/issue15298 http://bugs.python.org/issue15833 The only thing that stands

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Roundup Robot added the comment: New changeset e0a2b14a3cf9 by Trent Nelson in branch '2.7': Issue #15819: additional fixes for out-of-tree builds from read-only src. http://hg.python.org/cpython/rev/e0a2b14a3cf9 -- ___ Python tracker

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Roundup Robot added the comment: New changeset 617591e7d708 by Trent Nelson in branch '3.2': Issue #15819: additional fixes for out-of-tree builds from read-only src. http://hg.python.org/cpython/rev/617591e7d708 New changeset abb00e23681a by Trent Nelson in branch '3.3': Merge issue #15819: add

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Trent Nelson added the comment: > Since the committed patch is already a step in that direction, > I think it now needs to be completed. It's mandatory (IMO) > that the generated files are actually used; that the generators > are not run if not needed is optional and can be fixed later. Martin:

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Richard Oudkerk added the comment: I have opened a new issue: http://bugs.python.org/issue15833 It is a regression because in Python 3.2 all failures to open the file for writing were supressed. > But as I said: I'd also be fine with declaring this VM software > unsupported. If this work-

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin v. Löwis added the comment: Am 31.08.12 18:18, schrieb Eric Snow: > Doesn't EIO cover pathologies which we don't want to silence? I could see > adding EROFS though. [This should *really* be its own issue] Sure, EIO indicates normally something pathological, such as a broken cable to the

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Eric Snow added the comment: Doesn't EIO cover pathologies which we don't want to silence? I could see adding EROFS though. -- nosy: +eric.snow ___ Python tracker ___ _

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin v. Löwis added the comment: Am 31.08.12 17:32, schrieb Richard Oudkerk: >File "", line 128, in _write_atomic > OSError: [Errno 5] Input/output error: > '/mnt/hgfs/Repos/cpython-dirty/Lib/__pycache__/codecs.cpython-33.pyc.3076609376' > Aborted > > I took this to be a failure to write t

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Richard Oudkerk added the comment: It looks like the code which writes the byte-compiled codes checks for and ignores PermissionError (EACCES, EPERM) and FileExistsError (EEXIST). However, for me it is EIO which is raised. -- ___ Python tracker

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Richard Oudkerk added the comment: > Why is that? python will work just fine if it can't write pyc files. When I hacked around the _sysconfigdata.py issue, running the created python produced Fatal Python error: Py_Initialize: Unable to get the locale encoding Traceback (most recent call last)

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin v. Löwis added the comment: Am 31.08.12 16:40, schrieb Richard Oudkerk: > I suspect a bigger issue is the fact that *.pyc files cannot be > written to $(srcdir)/Lib/__pycache__. This means that to complete > the build, $(PYTHON_FOR_BUILD) should probably include the -B flag to > prevent i

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Richard Oudkerk added the comment: > Richard: what was your use case? Building on the main host and a VM without having to commit and synchronize temporary changes. (The VM has read-only access to the host's repositories). > What steps did you take that resulted in getting typeslots.inc and

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin v. Löwis added the comment: Am 31.08.12 15:19, schrieb Trent Nelson: > I think I should clarify my use case that resulted in raising this > bug. > > 1. Create a fresh hg clone, say, ~/hg/cpython-3.2. > 2. Make it readonly The use case is really uncontended, and long-standing. People want

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Trent Nelson added the comment: Well, that escalated quickly :-) I think I should clarify my use case that resulted in raising this bug. 1. Create a fresh hg clone, say, ~/hg/cpython-3.2. 2. Make it readonly: `zfs set readonly=on tank/home/cpython/hg/cpython-3.2` 3. cd /tmp/cpython-3.2-build 4.

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Changes by Andrew Svetlov : -- stage: committed/rejected -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin v. Löwis added the comment: Reconsidering more: it would be desirable if even an out-of-source-tree compilation wouldn't require Python for bootstrapping; with the committed patch, it does since it will always run ASDLGEN. If the source version of the generated files is fresh enough, th

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin v. Löwis added the comment: As a further follow-up: the original code (in 67ed8a6905c3, by Neil Schemenauer from 2001), he explicitly changed GRAMMAR_C/H to refer to srcdir, claiming that errors from building them would be ignored. In r87558, for which I can't find a subversion revsisio

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Ned Deily added the comment: The sysconfigdata problem is already documented in two open issues: Issue14774 and Issue15298. -- nosy: +ned.deily ___ Python tracker ___ __

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin v. Löwis added the comment: What I liked about Trent's original bug report is that it didn't just bring up a generic issue (cannot build with read-only source code), but clarified that his concern really was graminit. So I'd like to declare that this (graminit) is the focus of this issu

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Richard Oudkerk added the comment: I tried building from out-of-tree with a read-only srcdir, but I found two other files which the build process tries to create in the source directory: $(srcdir)/Objects/typeslots.inc $(srcdir)/Lib/_sysconfigdata.py -- nosy: +sbt

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Changes by Trent Nelson : -- stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___ ___ Python-bugs-l

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Roundup Robot added the comment: New changeset 2dde5a7439fd by Trent Nelson in branch '2.7': Issue #15819: Fix out-of-tree builds from a readonly source. http://hg.python.org/cpython/rev/2dde5a7439fd -- ___ Python tracker

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Roundup Robot added the comment: New changeset ab6ab44921b2 by Trent Nelson in branch 'default': Issue #15819: Fix out-of-tree builds from a readonly source. http://hg.python.org/cpython/rev/ab6ab44921b2 -- ___ Python tracker

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Roundup Robot added the comment: New changeset af36536988fd by Trent Nelson in branch 'default': Block 78809:62044cd5b19b (Issue #15819) from 3.2. http://hg.python.org/cpython/rev/af36536988fd -- ___ Python tracker

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Roundup Robot added the comment: New changeset 62044cd5b19b by Trent Nelson in branch '3.2': Issue #15819: Fix out-of-tree builds from a readonly source. http://hg.python.org/cpython/rev/62044cd5b19b -- nosy: +python-dev ___ Python tracker

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin v. Löwis added the comment: Am 30.08.12 09:47, schrieb Trent Nelson: > Objections to backporting to 3.2? > > Is 2.7 off the table? No, adding AC_PROG_MKDIR_P into all of them is fine. -- ___ Python tracker

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Trent Nelson added the comment: Ah, I see the MKDIR_P changes in 3.x/configure as well. Objections to backporting to 3.2? Is 2.7 off the table? (Building from a readonly source is handy for Snakebite; saves having a dozen machines needing to use their own hg clone.) -- _

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Petri Lehtinen added the comment: In 3.3, Makefile.pre.in already defines MKDIR_P, in 3.2 it doesn't. -- nosy: +petri.lehtinen ___ Python tracker ___

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Trent Nelson added the comment: That's what I figured you meant initially... Until I couldn't find any MKDIR_P definitions, and couldn't get it working without the hack above. I thought it might be an implicit make variable as well, but, not so much. (Tested with BSD make and gmake on FreeBSD

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin v. Löwis added the comment: Am 30.08.12 09:19, schrieb Trent Nelson: > Hm. Now I'm confused. Is this what you meant? No. Makefile.pre.in *already* has a definition of MKDIR_P, no need to add one. -- title: Unable to build Python out-of-tree when source tree is readonly. ->

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Trent Nelson added the comment: Hm. Now I'm confused. Is this what you meant? --- % hg diff diff -r 019a2390b014 Makefile.pre.in --- a/Makefile.pre.in Tue Aug 21 23:41:43 2012 + +++ b/Makefile.pre.in Thu Aug 30 07:16:55 2012 + @@ -43,6 +43,8 @@ GNULD=

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Martin v. Löwis added the comment: Instead of using "mkdir -p", it should use $(MKDIR_P) (which actually isn't normally "mkdir -p" :-) Other than that, the patch looks fine. -- nosy: +loewis ___ Python tracker ___

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

Changes by Trent Nelson : -- stage: needs patch -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15819] Unable to build Python out-of-tree when source tree is readonly.

New submission from Trent Nelson: This is somewhat related to Issue #9860. You can't currently build Python out-of-tree when the source directory is readonly. This is because there are a few Parser/pgen/AST/python_asdl.py steps that try and write to $(srcdir). The attached patch fixes this.