| 1 |
On 08/13/2010 03:34:21 AM, Christopher Schwan wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> On Friday 13 August 2010 00:54:53 Steven Trogdon wrote: |
| 5 |
>> Hi Christopher, |
| 6 |
>> |
| 7 |
>> On 08/12/2010 03:16:44 PM, Christopher Schwan wrote: |
| 8 |
>> > Hi, |
| 9 |
>> > |
| 10 |
>> > On Thursday 12 August 2010 17:37:34 Steven Trogdon wrote: |
| 11 |
>> >> Hi: |
| 12 |
>> >> |
| 13 |
>> >> I had apparently installed the Sage-provided scripts |
| 14 |
>> >> |
| 15 |
>> >> sage-g77_shared |
| 16 |
>> >> sage_fortran |
| 17 |
>> |
| 18 |
>> <SNIP> |
| 19 |
>> |
| 20 |
>> > Thats absolutely right - thank you for pointing that out. I have added |
| 21 |
>> > these files for now, but I think I will write a fix so we wont need |
| 22 |
>> > these. |
| 23 |
>> > |
| 24 |
>> >> Steve |
| 25 |
>> > |
| 26 |
>> > Christopher |
| 27 |
>> |
| 28 |
>> Relative to the included files, it appears that with the Sage-provided |
| 29 |
>> sage-g77_shared script, sage_fortran can't just point to the fortran |
| 30 |
>> compiler since sage_fortran needs to have arguments, i.e. the "$@" is |
| 31 |
>> needed in using sage_fortran. |
| 32 |
> |
| 33 |
> "$@" just adds the command line arguments given to sage_fortran to fortran, |
| 34 |
> which is what a symlink implicitly does. |
| 35 |
> |
| 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 |
>> |
| 47 |
>> Steve |
| 48 |
> |
| 49 |
> Christopher |
| 50 |
> |
| 51 |
|
| 52 |
Steve |
Archives