These are copied during the build process:

$ egrep -r partitions_c.h logs/install.log 
copying 
/home/vbraun/Sage/git-develop/src/build/cythonized/sage/combinat/partitions_c.h 
-> 
/home/vbraun/Sage/git-develop/local/lib/python2.7/site-packages/sage/combinat

Can you post your logs/pkgs/sagelib-7.3.beta2.log and whats the output of 

sage: from sage_setup.find import find_extra_files
sage: from sage.env import SAGE_SRC, SAGE_CYTHONIZED
sage: find_extra_files(["sage.combinat"], SAGE_SRC, SAGE_CYTHONIZED, ".")
[('./sage/combinat',
  ['/home/vbraun/Code/sage/src/sage/combinat/combinat_cython.pxd',
   '/home/vbraun/Code/sage/src/sage/combinat/enumeration_mod_permgroup.pxd',
   '/home/vbraun/Code/sage/src/sage/combinat/permutation_cython.pxd',
  
 '/home/vbraun/Code/sage/src/build/cythonized/sage/combinat/partitions_c.h'])]



On Monday, May 30, 2016 at 12:02:31 AM UTC+2, paulmasson wrote:
>
> Turns out this issue has nothing to do with the Github copy. I downloaded 
> a 7.2 tarball and had the same issue a total of nine times. Here are the 
> successive error messages:
>
> /Users/Masson/desktop/sage/src/build/cythonized/sage/combinat/partitions.cpp:323:26:
>  
> fatal error: partitions_c.h: No such file or directory
>
>  #include "partitions_c.h"
>
> /Users/Masson/desktop/sage/src/build/cythonized/sage/combinat/matrices/dancing_links.cpp:319:29:
>  
> fatal error: dancing_links_c.h: No such file or directory
>
>  #include "dancing_links_c.h"
>
> /Users/Masson/desktop/sage/src/build/cythonized/sage/graphs/base/boost_graph.cpp:314:31:
>  
> fatal error: boost_interface.cpp: No such file or directory
>
>  #include "boost_interface.cpp"
>
> /Users/Masson/desktop/sage/src/build/cythonized/sage/libs/ecl.c:324:20: 
> fatal error: eclsig.h: No such file or directory
>
>  #include "eclsig.h"
>
> /Users/Masson/desktop/sage/src/build/cythonized/sage/libs/ppl.cpp:336:23: 
> fatal error: ppl_shim.hh: No such file or directory
>
>  #include "ppl_shim.hh"
>
> /Users/Masson/desktop/sage/src/build/cythonized/sage/libs/eclib/mwrank.cpp:356:20:
>  
> fatal error: wrap.cpp: No such file or directory
>
>  #include "wrap.cpp"
>
> /Users/Masson/desktop/sage/src/build/cythonized/sage/matroids/matroid.c:296:22:
>  
> fatal error: minorfix.h: No such file or directory
>
>  #include "minorfix.h"
>
> /Users/Masson/desktop/sage/src/build/cythonized/sage/misc/darwin_utilities.c:290:33:
>  
> fatal error: darwin_memory_usage.h: No such file or directory
>
>  #include "darwin_memory_usage.h"
>
> /Users/Masson/desktop/sage/src/build/cythonized/sage/symbolic/pynac.cpp:334:22:
>  
> fatal error: pynac_cc.h: No such file or directory
>
>  #include "pynac_cc.h"
>
> After each failed build I manually copied each missing file to the 
> appropriate directory and ran 'make' again. I now have a running build of 
> 7.2. Yippee!
>
> A friend has suggested that the errors might be caused by bad line endings 
> that only show up on a Mac. Any other explanations for such apparently 
> random behavior?
>
>
> On Saturday, May 28, 2016 at 5:55:04 PM UTC-7, paulmasson wrote:
>>
>> Running OS X El Capitan on a year-old Macbook.
>>
>> Deleted my entire Sage directory. Did a clean clone from 
>> github.com/sagemath/sage.git. Immediately changed to Sage directory and 
>> ran make. Same error as previously:
>>
>> error: command 'gcc' failed with exit status 1
>>
>> /Users/Masson/downloads/github/sage/src/build/cythonized/sage/combinat/partitions.cpp:323:26:
>>  
>> fatal error: partitions_c.h: No such file or directory
>>
>>  #include "partitions_c.h"
>>
>>                           ^
>>
>> compilation terminated.
>>
>> make[3]: *** [sage] Error 1
>>
>>
>> Is there a problem building from the github copy?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Reply via email to