On 30 November 2010 09:12, Jean-Pierre Flori wrote:
>
>
> On 30 nov, 00:34, David Kirkby wrote:
>> On 29 November 2010 14:49, Jean-Pierre Flori wrote:
>>
>> > It now fails when building sqlite:
>>
>> > /usr/local/gcc4/bin/gcc -DPACKAGE_NAME=\"sqlite\" -DPACKAGE_TARNAME=
>>
>> how are you gettin
On 30 nov, 00:34, David Kirkby wrote:
> On 29 November 2010 14:49, Jean-Pierre Flori wrote:
>
> > It now fails when building sqlite:
>
> > /usr/local/gcc4/bin/gcc -DPACKAGE_NAME=\"sqlite\" -DPACKAGE_TARNAME=
>
> how are you getting Sage to build with a gcc in /usr/local/gcc4/bin/ ?
>
> If you
On 29 November 2010 14:49, Jean-Pierre Flori wrote:
> It now fails when building sqlite:
>
> /usr/local/gcc4/bin/gcc -DPACKAGE_NAME=\"sqlite\" -DPACKAGE_TARNAME=
how are you getting Sage to build with a gcc in /usr/local/gcc4/bin/ ?
If you are doing what seems a logical thing to do (set the CC
It now fails when building sqlite:
/usr/local/gcc4/bin/gcc -DPACKAGE_NAME=\"sqlite\" -DPACKAGE_TARNAME=
\"sqlite\" -DPACKAGE_VERSION=\"3.6.22\" "-DPACKAGE_STRING=\"sqlite
3.6.22\"" -DPACKAGE_BUGREPORT=\"http://www.sqlite.org\"; -DPACKAGE=
\"sqlite\" -DVERSION=\"3.6.22\" -D_FILE_OFFSET_BITS=64 -
D
Hi,
As stated in trac #10187 , I was unable to run Maxima's doctest, so I
began compiling Sage 4.6.1.alpha2 from source.
I do it one the T5140 because I have access to libgfortran there and a
recent enough perl there, but not on the sunblade 1500.
When compiling patch spkg I got the following err
Hi,
Everything runs fine now (after fighting with nfs).
I've even built the new maxima and ecl, patched everything (one hunk
failed, looked at it, it must be a test which has benn added after
4.5.1 release...)
I'm now trying to run doctests of interfaces/maxima.py.
I'll run it on the Sunblade 1500
On 18 November 2010 13:07, Jean-Pierre Flori wrote:
> You were right, there is something wrong with the libgfortran file
> under SAGE_ROOT/local/lib/ .
> It was a symlink to "./../lib/libgfortran.so", strange.
>
> Sage is working with the libraries you posted above. Thanks !
I'll need to make sur
On 18 November 2010 09:01, Jean-Pierre Flori wrote:
> Hi,
>
>> Can you send me the output of
>>
>> $ gcc -v
>> $ gfortran -v
>> $ command -v gcc
>> $ cmmand -v gfortran
>>
>> on your system.
>>
> Here it is:
> bash-3.00$ gcc -v
> Reading specs from /usr/local/packages/gcc3/bin/../lib/gcc/sparc-sun
You were right, there is something wrong with the libgfortran file
under SAGE_ROOT/local/lib/ .
It was a symlink to "./../lib/libgfortran.so", strange.
Sage is working with the libraries you posted above. Thanks !
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscri
Hi,
> Can you send me the output of
>
> $ gcc -v
> $ gfortran -v
> $ command -v gcc
> $ cmmand -v gfortran
>
> on your system.
>
Here it is:
bash-3.00$ gcc -v
Reading specs from /usr/local/packages/gcc3/bin/../lib/gcc/sparc-sun-
solaris2.10/3.4.3/specs
Configured with: /sfw10/builds/build/sfw10-pa
On 18 November 2010 00:59, David Kirkby wrote:
> On 17 November 2010 23:56, Jean-Pierre Flori wrote:
> PS, when you first run Sage, you will need to have /opt/ccs/bin in
> your path, so Sage can find 'm4', which it needs whenever a build of
> Sage is moved.
>
> Dave
Correction. You will need /u
On 17 November 2010 23:56, Jean-Pierre Flori wrote:
> Thanks for taking care of this !
>
> I was just trying to run tests on Solaris for the next Ecl and Maxima
> spgk's...
>
> I'll try downlaoding your lib tomorrow, I'm not at work right now and
> am too tired to ssh and etc...
No problem.
> Ju
Thanks for taking care of this !
I was just trying to run tests on Solaris for the next Ecl and Maxima
spgk's...
I'll try downlaoding your lib tomorrow, I'm not at work right now and
am too tired to ssh and etc...
Just one point: we've got a quite recent gcc installed on our Solaris,
I'd say gcc
13 matches
Mail list logo
