Volker,
> If the directory is already in the built-in search path (like
> /Users/minshall/src/import/sage/sage-5.4.1/local/include if you use
> the gcc that Sage compiled) then the -I option is ignored.
ah! got it. so, the Sage-compiled gcc includes .../local/include as
"a standard system direc
If the directory is already in the built-in search path (like
/Users/minshall/src/import/sage/sage-5.4.1/local/include if you use the gcc
that Sage compiled) then the -I option is ignored.
-Idir
Add the directory dir to the head of the list of directories to be searched
for header files. This
Volker,
No its first -I, 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.
however, this doesn't explain the failure i was having, where
gcc -c -I. -I../src/headers -I../src/la
No its first -I, 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
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
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.
--
You received this message because you are subscribed to the Google Groups
"sage-su
Jeroen Demeyer writes:
> Could you list your environment variables within Sage?
Script started on Fri Dec 14 09:12:28 2012
bash greg-minshalls-mbp: {500} ./sage -sh
Starting subshell with Sage environment variables set. Don't forget
to exit when you are done. Beware:
* Do not do anything with
Hi, Greg,
On Dec 13, 2012, at 10:39 , Greg Minshall wrote:
> i still don't know what causes this problem. but, i created a new user on
> my machine with a very bland environment, and ran the build from there.
> while the build is not yet finished, PARI/GP built just fine.
Everything in the c
i still don't know what causes this problem. but, i created a new user on
my machine with a very bland environment, and ran the build from there.
while the build is not yet finished, PARI/GP built just fine.
(as i said, i *did* move fink, etc., out of the way, but the build still
failed. so,
