[sage-devel] Re: including malloc.h on OSX vs. Linux

2010-05-15 Thread Nathan O'Treally
On 16 Mai, 06:43, Jason Grout wrote: > On 5/15/10 11:32 PM, Justin C. Walker wrote: > > >> Surely this is not the first time this problem has been run into among > >> this crowd. How is this typically dealt with when compiling a C file? > >> Should I make a new include directory in module_list.p

Re: [sage-devel] Re: including malloc.h on OSX vs. Linux

2010-05-15 Thread Robert Bradshaw
On May 15, 2010, at 9:43 PM, Jason Grout wrote: On 5/15/10 11:32 PM, Justin C. Walker wrote: Surely this is not the first time this problem has been run into among this crowd. How is this typically dealt with when compiling a C file? Should I make a new include directory in module_list.py

[sage-devel] Re: including malloc.h on OSX vs. Linux

2010-05-15 Thread Jason Grout
On 5/15/10 11:32 PM, Justin C. Walker wrote: Surely this is not the first time this problem has been run into among this crowd. How is this typically dealt with when compiling a C file? Should I make a new include directory in module_list.py (where the appropriate .pyx files are compiled with t

[sage-devel] Re: including malloc.h on OSX vs. Linux

2010-05-15 Thread Nathan O'Treally
On 16 Mai, 05:03, Jason Grout wrote: > In fixing #8756, I've upgraded the graph planarity code to the most > recent rewrite of John Boyer's planarity code.  Unfortunately, the C > code has several instances of: > > #include > > I just found out that OSX does not like this, where it should apparen