From: Steven Trogdon <strogdon@d.umn.edu>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] [sage-on-gentoo] fortran scripts
Date: Fri, 13 Aug 2010 07:20:45 -0500 [thread overview]
Message-ID: <1281702054.7123.0@pavilion64> (raw)
In-Reply-To: <201008131034.21870.cschwan@students.uni-mainz.de> (from cschwan@students.uni-mainz.de on Fri Aug 13 03:34:21 2010)
[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]
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 #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-08-13 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 15:37 [gentoo-science] [sage-on-gentoo] fortran scripts Steven Trogdon
2010-08-12 20:16 ` Christopher Schwan
2010-08-12 22:54 ` Steven Trogdon
2010-08-13 8:34 ` Christopher Schwan
2010-08-13 12:20 ` Steven Trogdon [this message]
2010-08-13 14:32 ` Christopher Schwan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1281702054.7123.0@pavilion64 \
--to=strogdon@d.umn.edu \
--cc=gentoo-science@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox