sage-2.10.4 on opensuse 10.3

10 views
Skip to first unread message

Florin

unread,
Mar 24, 2008, 8:38:40 AM3/24/08
to sage-support
Hi,

Several problems I encountered while building sage-2.10.4 on opensuse
10.3:

1. make fails because the scons tool is hardwired to use -no_archive
option for ld.
This option is not valid for the version of ld in openSuSE 10.3.
Simple workaround: do a first build that fails, remove -no_archive
flag
from local/lib/scons-0.97/SCons/Tool/ifort.py, then redo the build
that
will finish successfully.

2. "make test" fails on most tests with the error:
ImportError: /usr/local/sage-2.10.4/local/lib/libcsage.so: undefined
symbol: __dso_handle

3. "make html" and "make pdf" fail because \@mathbf cannot be handled.

I understand that some of these errors may be because of various bugs
or unimplemented features in opensuse 10.3, still some decent
workarounds would be highly appreciated.
Thank you very much,

Florin Manolache

mabshoff

unread,
Mar 24, 2008, 8:45:00 AM3/24/08
to sage-support


On Mar 24, 1:38 pm, Florin <florinm...@gmail.com> wrote:
> Hi,

Hi Florin,

> Several problems I encountered while building sage-2.10.4 on opensuse
> 10.3:
>
> 1. make fails because the scons tool is hardwired to use -no_archive
> option for ld.
> This option is not valid for the version of ld in openSuSE 10.3.
> Simple workaround: do a first build that fails, remove -no_archive
> flag
> from local/lib/scons-0.97/SCons/Tool/ifort.py, then redo the build
> that
> will finish successfully.

The issue here is that you have the Intel Fortran compiler installed.
For some stupid reason SCons selects that as the default fortran
compiler regardless whether gfortran or g95 is installed. I thing it
is time that we fix that issue once and for all by teaching SCons not
to use the Intel compiler. That is #1618. I will likely fix that
today since it has come up over and over again.

> 2. "make test" fails on most tests with the error:
>  ImportError: /usr/local/sage-2.10.4/local/lib/libcsage.so: undefined
> symbol: __dso_handle

This is likely caused by the Intel Fortran compiler.

> 3. "make html" and "make pdf" fail because \@mathbf cannot be handled.

Got any more details?

> I understand that some of these errors may be because of various bugs
> or unimplemented features in opensuse 10.3, still some decent
> workarounds would be highly appreciated.
> Thank you very much,

Not sure what the problem could be in this case, but my guess is that
some essential TeX macro package is missing. I remember the days when
SuSE installed a decent TeX per default, but those days are long gone
and it has been a while since TeX is installed per default at all.

> Florin Manolache

Cheers,

Michael

Florin

unread,
Mar 24, 2008, 9:04:33 AM3/24/08
to sage-support
Hi Michael,

Thank you for the quick reply.

> Got any more details?

! Undefined control sequence.
<recently read> \@mathbf

l.261 ...bf {Z}$ of Integers}}{1695}{section.24.1}

?
! Emergency stop.
<recently read> \@mathbf

l.261 ...bf {Z}$ of Integers}}{1695}{section.24.1}

! ==> Fatal error occurred, no output PDF file produced!

> Not sure what the problem could be in this case, but my guess is that
> some essential TeX macro package is missing. I remember the days when
> SuSE installed a decent TeX per default, but those days are long gone
> and it has been a while since TeX is installed per default at all.

Indeed opensuse 10.3 replaced tetex by texlive, which is incomplete
and introduces lots of backwards compatibility issues.
I will keep digging into that and hopefully find out what's missing.
This problem is not so important for the moment, just thought I would
mention it for future reference :)

Best regards,
Florin Manolache

Carl Witty

unread,
Mar 24, 2008, 10:47:58 AM3/24/08
to sage-support
On Mar 24, 5:38 am, Florin <florinm...@gmail.com> wrote:
> 3. "make html" and "make pdf" fail because \@mathbf cannot be handled.

You just need to delete devel/doc-main/ref/ref.aux and .../ref.toc and
try again. (These cache files should not be distributed at all; and
they seem not to be present in my copy of 2.11.alpha0.)

Carl

Florin

unread,
Mar 26, 2008, 12:18:40 PM3/26/08
to sage-support
Thanks everybody for your help.

Following the advice here, these are the solutions that worked out for
me:

1,2. Eliminating the Intel compilers from the path resulted in a clean
build of sage, all the tests were successful..

3. removing the .aux and .toc cache files from the documentation area
solved the pdf/html problems.

Florin

mabshoff

unread,
Mar 26, 2008, 12:29:33 PM3/26/08
to sage-support


On Mar 26, 5:18 pm, Florin <florinm...@gmail.com> wrote:
> Thanks everybody for your help.
>
> Following the advice here, these are the solutions that worked out for
> me:
>
> 1,2. Eliminating the Intel compilers from the path resulted in a clean
> build of sage, all the tests were successful..

Ok, the issue has been fixed in 2.11 and should no longer happen. I
consider that an SCons bug. Amazingly the SCons release from Dec. 2007
does not support gfortran nor g95!

> 3. removing the .aux and .toc cache files from the documentation area
> solved the pdf/html problems.

ok, we ought to make sure that we remove all those temp files before
packaging the documentation.

> Florin

Cheers,

Michael

William Stein

unread,
Mar 26, 2008, 2:32:12 PM3/26/08
to sage-s...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages