Hi Peter,
On Tue, Mar 20, 2012 at 15:17, Peter Cock wrote:
>> You don't need it: just run translate.py targetrichards.py
>> and you'll get a targetrichards-c executable.
>
> Doing that I do get a testing_1.dylib file (Mach-O 64-bit
> dynamically linked shared library x86_64) under a temp
> folder
On Tue, Mar 20, 2012 at 12:40 PM, Antonio Cuni wrote:
> On 03/20/2012 12:51 PM, Peter Cock wrote:
>>
>> Next, using the Richards example (short but non-trivial),
>>
>> $ cd pypy/translator/goal
>> $ python translate.py --run targetrichards.py
>
> I never heard of the --run option before :-)
It se
On Tue, Mar 20, 2012 at 4:40 PM, Peter Cock wrote:
> Hi again,
>
> Based on the structure of pypy/translator/goal/richards.py and
> pypy/translator/goal/targetrichards.py I have tried to make a
> simple ZLIB based benchmark based on what I have been using.
>
> $ python2.6 green_bottles.py
> Green
Hi again,
Based on the structure of pypy/translator/goal/richards.py and
pypy/translator/goal/targetrichards.py I have tried to make a
simple ZLIB based benchmark based on what I have been using.
$ python2.6 green_bottles.py
Green bottles ZLIB benchmark starting... []
Trying ZLIB on 176683 bytes
On Tue, Mar 20, 2012 at 12:40 PM, Antonio Cuni wrote:
> On 03/20/2012 12:51 PM, Peter Cock wrote:
>>
>> Next, using the Richards example (short but non-trivial),
>>
>> $ cd pypy/translator/goal
>> $ python translate.py --run targetrichards.py
>
> I never heard of the --run option before :-)
It se
On 03/20/2012 12:51 PM, Peter Cock wrote:
> Hi all,
>
> After a teething error with PyPy calling GCC with unescaped paths,
> which I solved by moving to a directory without spaces in the full
> path, I made some progress.
>
> First, get PyPy from hg - perhaps checking out a known good
> revision:
On Tue, Mar 20, 2012 at 11:51 AM, Peter Cock wrote:
> Hi all,
>
> After a teething error with PyPy calling GCC with unescaped paths,
> which I solved by moving to a directory without spaces in the full
> path, I made some progress.
>
> ...
>
> $ python translate.py --run targetreallynopstandalone.
Hi all,
After a teething error with PyPy calling GCC with unescaped paths,
which I solved by moving to a directory without spaces in the full
path, I made some progress.
First, get PyPy from hg - perhaps checking out a known good
revision:
$ hg clone http://bitbucket.org/pypy/pypy pypy
$ cd pypy
Hi,
turns out the git repo is not entirely compatible with recent hg-git
so there is a divergence of dozens of commits being replicated,
also there are some direct defects on metadata
i cant recommend working that way,
a possible mode of operation could be hacking in git,
then importing patche
Hi.
On Tue, Mar 20, 2012 at 3:36 PM, Roberto De Ioris wrote:
>
>
> > Hi all.
> >
> > I want to embed pypy into c code, but in pypy's directory, i don't find
> any pypy's c api, except in cypext directory.
> >
> > And I want to use stackless' c api too,. but i still have not found any
> stackles
> What kills me is the amount of time taken to rebuild the whole library, so
> i can work on it only on spare time (i am porting both mod_wsgi and uWSGI)
> :)
That's really cool! Didn't know someone is working on it. Can I direct
people with questions about that somewhere?
Cheers,
fijal
_
> Hi all.
>
> I want to embed pypy into c code, but in pypy's directory, i don't find
any pypy's c api, except in cypext directory.
>
> And I want to use stackless' c api too,. but i still have not found any
stackless api(example stackless_api.h) in pypy.
>
> Thanks.
>
> --
>
Currently you are
Hi all.
I want to embed pypy into c code, but in pypy's directory, i don't find
any pypy's c api, except in cypext directory.
And I want to use stackless' c api too,. but i still have not found any
stackless api(example stackless_api.h) in pypy.
Thanks.
--
do not fear to be eccentric in opin
13 matches
Mail list logo