No its first -I<dir>, then *_INCLUDE_PATH, then the path thats hard-wired into the compiler. But since Sage builds its own compiler you are effectively overriding the search path.
On Friday, December 14, 2012 3:13:06 PM UTC, Greg Minshall wrote: > > C_INCLUDE_PATH / CPLUS_INCLUDE_PATH are overriding the default gcc > header > > search path. This is why compilation is failing. Did fink put in these > > system-wide environment variables? Thats seriously effed up. > > no, they come from my .bashrc. they've been "there" since 2008. sadly, > i no longer remember (nor documented) the reason they ended up there. > > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To post to this group, send email to sage-support@googlegroups.com. To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support?hl=en.
