On 06/13/10 01:44 AM, orca wrote:
Ok Hart
I have now changed the make command to:
make CC=c99 FC=gfortran-4.2
and a new error emerges:
I've told you. You are wasting your time trying to set CC. I've set CC to be the
Sun Studio compiler, but gcc still gets called many times. Some parts of Sage
ignore CC, others follow it fully. Other parts have a mixture.
You should get yourself a setup so that typing
gcc, g++ or gfortran gives you identical versions.
Forget trying to set CC - it might work for some bits of Sage, but it will not
be consistent.
Dave
libtool: link: `/home/orca/sage/sage-4.4.3/spkg/build/
freetype-2.3.5.p2/src/objs/ftsystem.lo' is not a valid libtool object
make[2]: *** [/home/orca/sage/sage-4.4.3/spkg/build/freetype-2.3.5.p2/
src/objs/libfreetype.la] Error 1
make[2]: Leaving directory `/home/orca/sage/sage-4.4.3/spkg/build/
freetype-2.3.5.p2/src'
real 0m29.418s
user 0m22.877s
sys 0m4.668s
sage: An error occurred while installing freetype-2.3.5.p2
Please email sage-devel http://groups.google.com/group/sage-devel
explaining the problem and send the relevant part of
of /home/orca/sage/sage-4.4.3/install.log. Describe your computer,
operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/home/orca/sage/sage-4.4.3/spkg/build/freetype-2.3.5.p2 and type 'make
check' or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
(cd '/home/orca/sage/sage-4.4.3/spkg/build/freetype-2.3.5.p2'&& '/
home/orca/sage/sage-4.4.3/sage' -sh)
When you are done debugging, you can type "exit" to leave the
subshell.
make[1]: *** [installed/freetype-2.3.5.p2] Error 1
make[1]: Leaving directory `/home/orca/sage/sage-4.4.3/spkg'
real 1m4.089s
user 0m54.599s
sys 0m6.140s
Error building Sage.
./sage -docbuild all html 2>&1 | tee -a dochtml.log
python: can't open file '/home/orca/sage/sage-4.4.3/devel/sage/doc/
common/builder.py': [Errno 2] No such file or directory
Any new directions please???
On Jun 12, 9:10 pm, Bill Hart<goodwillh...@googlemail.com> wrote:
FLINT needs to compile with the -std=c99 flag. I presume someone
overrode it somehow, which breaks the build.
Bill.
On Jun 12, 11:46 pm, orca<mocal...@gmail.com> wrote:
Ok Marik
I checked that the default g++ under lenny is said to be 4.3.2,
despite the fact that in mine it is 4.2.4 and I'm sure I did not
change this myself...
At any rate, I do not think this has any relationship to the failure
of installation of flint, which is my current problem now; do you??
On Jun 12, 6:51 pm, "ma...@mendelu.cz"<ma...@mendelu.cz> wrote:
On 12 čvn, 23:30, orca<mocal...@gmail.com> wrote:
Dear Sirs,
I have a palin vanilla Debian lenny amd64 machine, which I use for
quite some time now; I am reasonably conversant (but not much) with
some installation commands for programs in general.
I have just tried to compile Sage 4.4.3 from source under that
machine. I had to circumvent some "small" issues:
1) I had to change the make command to
make CC=gcc-4.2 FC=gfortran-4.2
since the default vanilla C compiler, gcc, is version 4.3.2 and the
default vanilla Fortran compiler, gfortran, is version 4.3.2 as well,
whereas the default vanilla C++ compiler, g++, is version 4.2.4. So I
had to install these "downgraded" versions, which were available from
the official Debian lenny repos, without any ado...
Hi
As I wrote in sage-support, the default g++ is also version 4.3.2 ,
seehttp://packages.debian.org/lenny/g++
Robert
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
