1 |
On Friday 13 August 2010 14:20:45 Steven Trogdon wrote: |
2 |
> On 08/13/2010 03:34:21 AM, Christopher Schwan wrote: |
3 |
> > Hi, |
4 |
> > |
5 |
> > On Friday 13 August 2010 00:54:53 Steven Trogdon wrote: |
6 |
> >> Hi Christopher, |
7 |
> >> |
8 |
> >> On 08/12/2010 03:16:44 PM, Christopher Schwan wrote: |
9 |
> >> > Hi, |
10 |
> >> > |
11 |
> >> > On Thursday 12 August 2010 17:37:34 Steven Trogdon wrote: |
12 |
> >> >> Hi: |
13 |
> >> >> |
14 |
> >> >> I had apparently installed the Sage-provided scripts |
15 |
> >> >> |
16 |
> >> >> sage-g77_shared |
17 |
> >> >> sage_fortran |
18 |
> >> |
19 |
> >> <SNIP> |
20 |
> >> |
21 |
> >> > Thats absolutely right - thank you for pointing that out. I have added |
22 |
> >> > these files for now, but I think I will write a fix so we wont need |
23 |
> >> > these. |
24 |
> >> > |
25 |
> >> >> Steve |
26 |
> >> > |
27 |
> >> > Christopher |
28 |
> >> |
29 |
> >> Relative to the included files, it appears that with the Sage-provided |
30 |
> >> sage-g77_shared script, sage_fortran can't just point to the fortran |
31 |
> >> compiler since sage_fortran needs to have arguments, i.e. the "$@" is |
32 |
> >> needed in using sage_fortran. |
33 |
> > |
34 |
> > "$@" just adds the command line arguments given to sage_fortran to |
35 |
> > fortran, which is what a symlink implicitly does. |
36 |
> |
37 |
> Perhaps so, but things don't work as they are presently. Maybe the python |
38 |
> script messes up things. If I replace, in the sage-g77_shared script, |
39 |
> sage_fortran with the path to the fortran compiler then things work. The |
40 |
> symlink |
41 |
> |
42 |
> /usr/bin/sage_fortran -> x86_64-pc-linux-gnu-gfortran |
43 |
> |
44 |
> on my machine will then not be used. |
45 |
|
46 |
Ok I did that replacement - (should be) fixed in latest commit! |
47 |
|
48 |
> |
49 |
> >> Steve |
50 |
> > |
51 |
> > Christopher |
52 |
> |
53 |
> Steve |
54 |
|
55 |
Christopher |