Re: [pypy-dev] Separate building of the C source files

2011-09-16 Thread Armin Rigo
Hi Elad, On Wed, Sep 14, 2011 at 10:08 PM, Elad Lahav wrote: > Thanks, Armin, but that's the first place I looked. There is no makefile > there. Doesn't make much sense to me. A "Makefile" (not a "makefile") should be created. If it wasn't, then maybe it crashed during writing the C sources an

Re: [pypy-dev] Separate building of the C source files

2011-09-14 Thread Elad Lahav
Thanks, Armin, but that's the first place I looked. There is no makefile there. --Elad On Wed, Sep 14, 2011 at 3:57 PM, Armin Rigo wrote: > Hi Elad, > > On Wed, Sep 14, 2011 at 4:12 PM, Elad Lahav wrote: > > The source files were created under the /tmp directory. The first thing I > am > > mis

Re: [pypy-dev] Separate building of the C source files

2011-09-14 Thread Armin Rigo
Hi Elad, On Wed, Sep 14, 2011 at 4:12 PM, Elad Lahav wrote: > The source files were created under the /tmp directory. The first thing I am > missing, though, is a makefile. The Makefile should be in /tmp/usession-xxx/testing_1/. A bientôt, Armin. __

[pypy-dev] Separate building of the C source files

2011-09-14 Thread Elad Lahav
Hello, I am trying to build Pypy for an embedded platform, with its own build system. For that purpose, I would like to have the translation process run on a Linux/x86 box, generating the C source files, and then have the platform's own build system do C compilation and linking. With the 1.6 sourc