09.11.2013 13:20, David Seikel kirjoitti: > On Sat, 9 Nov 2013 11:48:41 +0100 Davide Andreoli > <d...@gurumeditation.it> wrote: > >> 2013/11/9 David Seikel <onef...@gmail.com> >> >>> On Thu, 17 Oct 2013 16:28:04 +0300 Kai Huuhko <kai.huu...@gmail.com> >>> wrote: >>> >>>> 17.10.2013 13:50, David Seikel kirjoitti: >>>>> On Thu, 17 Oct 2013 13:12:25 +0300 Kai Huuhko >>>>> <kai.huu...@gmail.com> wrote: >>>>> >>>>>> >>>>>> >>>>>> 17.10.2013 09:52, David Seikel kirjoitti: >>>>>>> On Thu, 17 Oct 2013 00:59:20 +0300 Kai Huuhko >>>>>>> <kai.huu...@gmail.com> wrote: >>>>>>> >>>>>>>> 15.10.2013 15:03, Kai Huuhko kirjoitti: >>>>>>>>> 15.10.2013 08:45, David Seikel kirjoitti: >>>>>>>>>> On Mon, 14 Oct 2013 23:31:08 +0300 Kai Huuhko >>>>>>>>>> <kai.huu...@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Let's just bump the minimum version requirement >>>>>>>>>>> already. ;) >>>>>>>>>> >>>>>>>>>> Ubuntu LTS still has cython 0.15.1. Will I ever be able to >>>>>>>>>> actually compile any of this python stuff? >>>>>>>>> >>>>>>>>> Patience, young Padawan. >>>>>>>>> >>>>>>>>> You may ask or wait for us to package the pre-generated >>>>>>>>> module C source files. >>>>>>>>> >>>>>>>>> I believe they recently added a target directory for the >>>>>>>>> generated files making it easier for us to do development >>>>>>>>> snapshots; Dave: could we automate this with Jenkins? >>>>>>>> >>>>>>>> First step of project onefanged python is complete: we can >>>>>>>> now create a source tarball with a single command. DaveMDS >>>>>>>> is now working on adding this step to Jenkins. >>>>>>>> >>>>>>>> Using this tarball you'll get the Python modules built >>>>>>>> without needing Cython at all. >>>>>>> >>>>>>> That wont help this onefang numbskull at all, he compiles from >>>>>>> git. >>>>>>> >>>>>> >>>>>> The barstand! >>>>>> >>>>>> Can't you modify the script to use these automated snapshots? >>>>> >>>>> Well I could, but I don't want to start special casing stuff in >>>>> my generic build script. Then every one will want it. :-P >>>>> >>>>>> The alternative is for us to keep the generated files in a >>>>>> branch, which can get messy. >>>>> >>>>> That wont work either, my generic build script specifically >>>>> uses the master branch. >>>>> >>>>>> (Or, we'll simply ignore you.) >>>>> >>>>> That's "worked" for years. :-P >>>>> >>>>> The big problem for me is that I have another project that uses >>>>> python, and it's important for that project to build on stock >>>>> standard Ubuntu LTS. So I can't just install the latest cython >>>>> and be done with it. No doubt when Ubuntu LTS gets refreshed >>>>> next year, EFL python's cython version requirement will move >>>>> out of reach. Again. >>>>> >>>> >>>> Not going to happen. Saucy already has Cython 0.19 and that's what >>>> we're planning to target here. We could go with 0.17 as well >>>> since we already worked around the problems that 0.18 and 0.19 >>>> solve. The version bump would simply mean that we can get rid of >>>> these "hacks". >>>> >>>>> I might see if I can simply install the latest cython in some >>>>> special place, then put that in the path for my EFL build >>>>> script. >>>>> >>>> >>>> Let me know how that works out. We'll have to figure out something >>>> else if it doesn't work. >>> >>> It half worked. I installed cython 0.19.1 from git source into my >>> home directory. Modified my build script to include that install >>> in the various python paths. The build works, but when I sudo to >>> root (using sudo -E to replicate the environment variables) to run >>> the install, it claims to not be able to find a recent enough >>> cython. I checked the python paths from sudo, they are the same. >>> >>> I don't have enough python fu to debug this. >>> >> >> I really suggest you to use the generated distribution package at: >> https://build.enlightenment.org/view/Base%20jobs/job/base_pyefl_build/lastSuccessfulBuild/artifact/dist/efl-1.7.99.tar.gz >> >> That one do NOT need cython, it is generated at every git push so it >> is always updated and, above all, you help us to test this package >> that will be the base for our future releases. >> >> I know you need to modify your build script for this but you modified >> it yet, so it is no more an excuse :P > > "Test the actual source code and process that is used to generate > the .c files" vs "test the distribution source package". Is really six > of one, half a dozen of the other. My build script is doing the first > for everything else, and specifically not building from source > tarballs. For the same reason that jenkins is building from git, not > from generated distribution source tarballs. Yes, testing the generated > source tarballs is a valuable thing to do, it's just not what this build > script is for though. > > I have entirely different scripts to build from released EFL source > tarballs, though obviously they don't cover as much as this build from > source repo script. These scripts don't compile the python stuff, but > that would be the place to use your pre generated Cython files. > > I think this "use a special cython version" method can be made workable. > It's doing the actual build fine, it's just the install that's going > wrong, and it's going wrong at the Cython stage, due to something > different in the sudo -E environment. Though the obvious first question > for me is - why is the install process needing Cython, should it have > already generated and compiled everything before this point? Why is > Cython needed at install time? If it's not, then perhaps your install > process needs changing?
We can't really do anything about it, as the build step can be made to run with the install command, and we need Cython for preprocessing the Cython source files into C source. We can skip Cython only when we're sure that it's purely building from C sources. > > If Cython IS needed at install time, then I gotta figure out what's > different in the sudo -E case. This might help others trying to > compile from git on other odd development environments. Though I still > maintain that Ubuntu LTS is not odd. :-P Pull the change I made to setup.py, let's see if the output can tell us more. > > > > ------------------------------------------------------------------------------ > November Webinars for C, C++, Fortran Developers > Accelerate application performance with scalable programming models. Explore > techniques for threading, error checking, porting, and tuning. Get the most > from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk > > > > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
