On 08/13/2010 03:34:21 AM, Christopher Schwan wrote:
Hi,

On Friday 13 August 2010 00:54:53 Steven Trogdon wrote:
Hi Christopher,

On 08/12/2010 03:16:44 PM, Christopher Schwan wrote:
> Hi,
>
> On Thursday 12 August 2010 17:37:34 Steven Trogdon wrote:
>> Hi:
>>
>> I had apparently installed the Sage-provided scripts
>>
>> sage-g77_shared
>> sage_fortran

        <SNIP>

> Thats absolutely right - thank you for pointing that out. I have added
> these files for now, but I think I will write a fix so we wont need
> these.
>
>> Steve
>
> Christopher

Relative to the included files, it appears that with the Sage-provided
sage-g77_shared script, sage_fortran can't just point to the fortran
compiler since sage_fortran needs to have arguments, i.e. the "$@" is
needed in using sage_fortran.

"$@" just adds the command line arguments given to sage_fortran to fortran,
which is what a symlink implicitly does.


Perhaps so, but things don't work as they are presently. Maybe the python script messes up things. If I replace, in the sage-g77_shared script, sage_fortran with the path to the fortran compiler then things work. The symlink

        /usr/bin/sage_fortran -> x86_64-pc-linux-gnu-gfortran

on my machine will then not be used.
        

Steve

Christopher


Steve

Attachment: pgpAtUqtzeYnG.pgp
Description: PGP signature

Reply via email to