On Sun, Feb 24, 2008 at 11:31 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > On Feb 24, 5:38 pm, mabshoff <[EMAIL PROTECTED] > > dortmund.de> wrote: > > On Feb 24, 12:05 pm, JMD <[EMAIL PROTECTED]> wrote: > > > > > > > > > on a linux-x86_64 machine > > > > > Installing c_lib > > > scons: `install' is up to date. > > > Traceback (most recent call last): > > > File "setup.py", line 1217, in <module> > > > deps = create_deps(ext_modules) > > > File "setup.py", line 1208, in create_deps > > > deps_graph(deps, f, visited) > > > File "setup.py", line 1175, in deps_graph > > > this_deps = search_all_includes(f) > > > File "setup.py", line 1099, in search_all_includes > > > S = open(filename).readlines() > > > IOError: [Errno 2] No such file or directory: 'sage-main/sage/modules/ > > > free_module_element.pyx' > > > sage: There was an error installing modified sage library code. > > > > > ERROR installing SAGE > > > > Hi, > > > > that is cause by #2180. There is a patch for it, but the short > > solution is to touch the pyrex file in question. Then everything is > > back to normal. > > > > Cheers, > > > > Michael > > Burcin did pop up in IRC a little while ago and reported the same > error. Neither touching the file, not a "sage -ba" nor applying the > patch from #2180 fixes the problem, so I am fresh out of ideas. It > only seems to happen on updates, i.e. in the other cases I saw the > issue a touching of a single file was sufficient. So there is maybe > more than one bug lurking in that code. Since I have been unable to > reproduce the harder problem yet any input (or even better solution) > is welcome :) >
Please try http://trac.sagemath.org/sage_trac/ticket/2296 William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
