Hi Georg,
The bug you remembered is http://sagetrac.org/sage_trac/ticket/3304, I
had not seen that report. I'll try to get it fixed now.
Volker
On Jan 27, 2:27 pm, "Georg S. Weber"
wrote:
> --- I consider the cddlib spkg example as another bug, and if I
> remember correctly, there already exis
> C-only libraries are ok. This bug must be some remnant of the build
> system, I don't have gcc installed under /usr/local (neither has the
> official Fedora 12).
>
> For example, $SAGE_ROOT/local/lib/libgmpxx.la contains:
>
> dependency_libs=' /home/vbraun/Sage/sage/local/lib/libgmp.la
> /usr/lo
Hi Mariha,
I'm not quite sure what you mean by compiler libraries; libstdc++.so
is installed in basically every unix and in the shared library search
path (save for embedded, perhaps). Even if you don't have a compiler
installed you pretty much need libstdc++.so or you can't run programs
that were
Volker,
Much thanks for your explanation.
So Sage binaries - since they depend on finding
dynamic compiler libraries like libstdc++.so - must be built
using compilers in standard locations on the build
machine, and the target
machines must have those same libraries in the same
standard locations.
Hi Mariah,
On Jan 26, 6:21 pm, Mariah wrote:
> I guess I do not understand that "usual drawbacks" to
> statically linking to which you refer. Can you expand, please?
First off all it wastes disk space; I'm trying to make a TOPCOM spkg
and a naive compile/make/make install will generate 200MB of
Volker,
I guess I do not understand that "usual drawbacks" to
statically linking to which you refer. Can you expand, please?
I still am confused about what is not working in Sage.
Are you talking about a program external to Sage not being
able to dynamically link with the Sage libraries?
Sorry
Hi Mariah,
The problem is that no program can dlink the (C++-using) libraries.
All existing spkgs apparently link statically which works but suffers
from the usual drawbacks. I've tried to modify cddlib to link
dynamically with gmp/mpir:
http://www.stp.dias.ie/~vbraun/cddlib-094f.p3.spkg
Now spk
Volker,
I am trying to understand what goes wrong by having the build compiler
in a non-standard place. (I am the sys admin for the particular
build machine in question.) Can you give me an example of
what Sage command or sequence of commands fails?
Mariah
On Jan 26, 7:43 am, Volker Braun wro
