Re: [pypy-dev] Cannot use MacPorts PyPy to Translate pypy-c

2013-09-11 Thread Armin Rigo
Hi Jean-François, On Tue, Sep 10, 2013 at 5:43 PM, Jean-François Caron wrote: > I can send an email or bug report to MacPorts, but I'm not sure how to > describe the bug, as I'm unfamiliar with the syslog module. Just reporting the error is plenty enough. The issue is that it's a CFFI module w

Re: [pypy-dev] LLVM next steps

2013-09-11 Thread Armin Rigo
Hi Eric, On Sun, Sep 8, 2013 at 7:00 PM, Eric van Riet Paap wrote: > What is the PyPy speed difference after using gcc versus llvm for the > compilation of the PyPy-c backend? Currently, it seems that using the LLVM IR static translation backend of PyPy gives higher performance. We're still tr

Re: [pypy-dev] Cannot use MacPorts PyPy to Translate pypy-c

2013-09-11 Thread Bengt Richter
Hi Armin, On 09/11/2013 09:10 AM Armin Rigo wrote: [...] Just reporting the error is plenty enough. The issue is that it's a CFFI module which gets built (by calling the C compiler) the first time it is imported. The library built is saved into some directory where (after installation) a norma

Re: [pypy-dev] Cannot use MacPorts PyPy to Translate pypy-c

2013-09-11 Thread Armin Rigo
Hi Bengt, On Wed, Sep 11, 2013 at 1:42 PM, Bengt Richter wrote: > Is it not currently possible to build and install everything pypy > in user mode, in a user directory, e.g. ~/.pypy/versionstring/... > and chmod selectively to protect against accidental mods/deletes? > > Will it not run properly