Volker, > 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. the gcc man page is a bit ambiguous: ---- CPATH C_INCLUDE_PATH CPLUS_INCLUDE_PATH OBJC_INCLUDE_PATH Each variable's value is a list of directories separated by a special character, much like PATH, in which to look for header files. The special character, "PATH_SEPARATOR", is target-dependent and determined at GCC build time. For Microsoft Windows-based targets it is a semicolon, and for almost all other targets it is a colon. CPATH specifies a list of directories to be searched as if specified with -I, but after any paths given with -I options on the command line. This environment variable is used regardless of which language is being preprocessed. The remaining environment variables apply only when preprocessing the particular language indicated. Each specifies a list of directories to be searched as if specified with -isystem, but after any paths given with -isystem options on the command line. ---- but i read (past and present tense) this as saying that C_INCLUDE_PATH is searched *after* any -I<dir> statements on the command lines (in which case, the -I<dir> statements Sage puts on the command line would have had the local directories searched before these). do you know, are they, in fact, search *before* the -I<dir>? that would certainly explain it. cheers, Greg -- 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.
