Jeroen, did you every try to build the gcc spkg with 

--with-native-system-header-dir=dirname   Specifies that dirname is the 
directory that contains native system header files, rather than 
/usr/include. This option is most useful if you are creating a compiler 
that should be isolated from the system as much as possible. It is most 
commonly used with the --with-sysroot option and will cause GCC to search 
dirname inside the system root specified by that option. 


On bsd.math, the gcc search path is


#include "..." search starts here:
#include <...> search starts here:
 
/Users/malb/sage-5.0.1-linbox/local/lib/gcc/x86_64-apple-darwin10.8.0/4.6.3/include
 /Users/malb/sage-5.0.1-linbox/local/include
 
/Users/malb/sage-5.0.1-linbox/local/lib/gcc/x86_64-apple-darwin10.8.0/4.6.3/include-fixed
 /usr/include
 /System/Library/Frameworks
 /Library/Frameworks


so I'm thinking we should

  * replace /usr/include with $SAGE_ROOT/local/include
  * and put a copy of Apple's /usr/include/limits.h there (BSD licenced)

A quick grep of gcc's include-fixed directory suggests that limits.h is the 
only header required (it is the only occurrence of #include_next, fwiw).

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
Visit this group at http://groups.google.com/group/sage-support?hl=en.


Reply via email to