William Stein wrote:
>>> have to explicitly tell the build process about the fortran
>>> compiler and library location. Do this by typing
>>>
>>> export SAGE_FORTRAN=/exact/path/to/gfortran
>>> export SAGE_FORTRAN_LIB=/path/to/fortran/libs/libgfortran.so
>>
>> Okay,
>> have to explicitly tell the build process about the fortran
>> compiler and library location. Do this by typing
>>
>> export SAGE_FORTRAN=/exact/path/to/gfortran
>> export SAGE_FORTRAN_LIB=/path/to/fortran/libs/libgfortran.so
>
>
> Okay, that worked. I didn't un
William Stein wrote:
> On Tue, Nov 17, 2009 at 1:05 PM, Jason Grout
> wrote:
>> François Bissey wrote:
>>> On Wed, 18 Nov 2009 08:23:39 Jason Grout wrote:
I have a fairly fresh installation of 64-bit Ubuntu 9.10, and I'm
compiling 4.2.1. I've installed gfortran and build-essential, plus
On Tue, Nov 17, 2009 at 1:05 PM, Jason Grout
wrote:
> François Bissey wrote:
>> On Wed, 18 Nov 2009 08:23:39 Jason Grout wrote:
>>> I have a fairly fresh installation of 64-bit Ubuntu 9.10, and I'm
>>> compiling 4.2.1. I've installed gfortran and build-essential, plus the
>>> other packages liste
On Wed, 18 Nov 2009 10:05:55 Jason Grout wrote:
>
> I haven't modified anything:
>
> /dev/shm/sage-4.2.1/local/bin% cat sage_fortran
>
> #!/bin/sh
>
> sage_fortran.bin -fPIC $...@%
>
>
>
> Of course, sage_fortran.bin is a binary executable.
>
> Checking the SAGE_FORTRAN bit:
>
> /dev/shm/s
François Bissey wrote:
> On Wed, 18 Nov 2009 08:23:39 Jason Grout wrote:
>> I have a fairly fresh installation of 64-bit Ubuntu 9.10, and I'm
>> compiling 4.2.1. I've installed gfortran and build-essential, plus the
>> other packages listed in step 1 of the README. I even set
>> SAGE_FORTRAN=/usr
