Hi,
what’s people’s experience with compiling cpython using multiple jobs
(e.g., make -j 8)?
In my case, I sometimes experience build errors that happen when using -j,
whereas the single-job build always works. I haven’t tracked this down in
detail, though… here’s an extract from a sample log:
1
Hi,
Thanks for your comments! I've done more tests on a new machine and, for
better or worse, was no longer able to reproduce the issue. Parallel
compilation now works fine; I'll keep collecting output from make, and
would post it here if the problem appears again.
One additional issue appeared,
>> > Would people be interested in having a parallel version?
>>
>> See http://bugs.python.org/issue5309
>
> Cool! I'll look into this.
The patch there works well for me. I've made one small update, and
submitted the new version in the bug tracker.
Regarding the other build problem, I might have
> > Would people be interested in having a parallel version?
>
> See http://bugs.python.org/issue5309
Cool! I'll look into this.
Just as I was thinking that the parallel build problems are solved,
the issue surfaced again. I've attached a complete, unmodified log to
this mail.
Some notes:
- asap
Hi again,
the attached Makefile patch seems to fix the parallel build problems.
Is there a chance of getting this into trunk? Should I open an issue
or send the patch somewhere else?
Cheers,
Jonas
On Fri, Sep 5, 2014 at 12:15 PM, Jonas Wagner wrote:
>>> > Would people be interest
Hi,
Open an issue on bugs.python.org and attach the patch there (it should also
> ask you so sign the contributor agreement, but if not then please also sign
> that).
>
Submitted as http://bugs.python.org/issue22359 , and signed the agreement.
Cheers,
Jonas
_
Hi,
Anyway, I think we must change CPython to support tools such as perf. Any
> thoughts?
>
Not many thoughts, other than that it would be nice to be able to use a
sampling profiler on Python code. I think this would especially benefit
applications that use libraries written in C, or applications
