I managed to get quite a way building 3.0.2 on my Solaris laptop
before there were any issues at all, but with 3.0.3.alpha0 things have
not gone so smoothly. However, I have very recently updated the
software on the laptop, so perhaps it is not Sage at fault.

The laptop is a dual core 2 GHz unit with an Intel CPU and 2 GB RAM.
It's running the Community Edition of Solaris Express and gcc 4.0.2.

What is odd, is that the point of failure (when configuring
gmp-4.2.2), if I go to the subshell:

 /export/home/drkirkby/sage-3.0.3.alpha0/sage -sh

then try to configure it, it goes ok!

bash-3.2$ cat /etc/release
                   Solaris Express Community Edition snv_89 X86
           Copyright 2008 Sun Microsystems, Inc.  All Rights Reserved.
                        Use is subject to license terms.
                              Assembled 06 May 2008


********* From the normal shell ****

x gmp-4.2.2/src/tune/sparcv9.asm, 1147 bytes, 3 tape blocks
x gmp-4.2.2/src/tune/speed-ext.c, 6962 bytes, 14 tape blocks
x gmp-4.2.2/src/tune/speed.c, 34941 bytes, 69 tape blocks
x gmp-4.2.2/src/tune/speed.h, 74541 bytes, 146 tape blocks
x gmp-4.2.2/src/tune/time.c, 46200 bytes, 91 tape blocks
x gmp-4.2.2/src/tune/tuneup.c, 49461 bytes, 97 tape blocks
x gmp-4.2.2/src/tune/x86_64.asm, 1392 bytes, 3 tape blocks
x gmp-4.2.2/src/version.c, 904 bytes, 2 tape blocks
Finished extraction
****************************************************
Host system
uname -a:
SunOS kingfisher 5.11 snv_89 i86pc i386 i86pc
****************************************************
****************************************************
GCC Version
gcc -v
Reading specs from /opt/csw/gcc4/lib/gcc/i386-pc-solaris2.8/4.0.2/
specs
Target: i386-pc-solaris2.8
Configured with: ../sources/gcc-4.0.2/configure --prefix=/opt/csw/gcc4
--with-local-prefix=/opt/csw --with-gnu-as --with-as=/opt/csw/bin/gas
--without-gnu-ld --with-ld=/usr/ccs/bin/ld --enable-threads=posix --
enable-shared --enable-multilib --enable-nls --with-included-gettext --
with-libiconv-prefix=/opt/csw --with-x --enable-java-awt=xlib --with-
system-zlib --enable-languages=c,c++,f95,java,objc,ada
Thread model: posix
gcc version 4.0.2
****************************************************
./spkg-install: gcc}: not found
Patching gmp-h.in (fixes OSX 10.5 issues and gcc 4.3 problems)
Fast gcd patch:
Moving files that are to be replaced to *.orig ...
Copying new files across...
Done.
checking build system type... core2-pc-solaris2.11
checking host system type... core2-pc-solaris2.11
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of
Makefiles... no
configure: error: ABI=32 is not among the following valid choices:
standard
Failed to configure.



**** Now from a subshell ****
bash-3.2$ /export/home/drkirkby/sage-3.0.3.alpha0/sage -sh

Starting subshell with Sage environment variables set.
Be sure to exit when you are done and do not do anything
with other copies of Sage!

Sage subshell$ cd /export/home/drkirkby/sage-3.0.3.alpha0/spkg/build/
gmp-4.2.2/src
Sage subshell$ ./configure
checking build system type... core2-pc-solaris2.11
checking host system type... core2-pc-solaris2.11
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of
Makefiles... no
checking ABI=standard


I've tried both Sun's make and GNU make. They both give the same
issue.

Any ideas??
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to