In Open Solaris in my VirtualBox running under Fedora 12 64 bit on an Intel i7 
860:

Finished extraction
****************************************************
Host system
uname -a:
SunOS opensolaris 5.11 snv_111b i86pc i386 i86pc Solaris
****************************************************
****************************************************
CC Version
gcc -v
Using built-in specs.
Target: i386-pc-solaris2.11
Configured with: ../gcc-4.3.4/configure --prefix=/usr/local/gcc-4.3.4-GNU-assembler-Sun-linker --with-as=/usr/local/binutils-2.20/bin/as --with-ld=/usr/ccs/bin/ld --with-gmp=/usr/local --with-mpfr=/usr/local
Thread model: posix
gcc version 4.3.4 (GCC)
****************************************************
Building 64 bit Solaris version
checking build system type... i486-pc-solaris2.11
checking host system type... i486-pc-solaris2.11
checking for a BSD-compatible install... /export/home/jaap/sage-bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
configure: error: ABI=64 is not among the following valid choices: 32
Failed to configure.

real    0m1.743s
user    0m0.190s
sys     0m0.466s
sage: An error occurred while installing mpir-1.2.2

While building the following SAGE related exports are set:
sage subshell$ env | grep SAGE
SAGE_SERVER=http://www.sagemath.org/
SAGE_ORIG_LD_LIBRARY_PATH_SET=True
SAGE_DATA=/export/home/jaap/Downloads/sage-4.3.1.alpha1/data
DOT_SAGE=/export/home/jaap/.sage/
SAGE_LOCAL=/export/home/jaap/Downloads/sage-4.3.1.alpha1/local
SAGE_STARTUP_FILE=/export/home/jaap/.sage//init.sage
LC_MESSAGES=en_US.UTF-8
SAGE_ROOT=/export/home/jaap/Downloads/sage-4.3.1.alpha1
SAGE_PACKAGES=/export/home/jaap/Downloads/sage-4.3.1.alpha1/spkg
SAGE_ORIG_LD_LIBRARY_PATH=
SAGE_DOC=/export/home/jaap/Downloads/sage-4.3.1.alpha1/devel/sage/doc
SAGE_TESTDIR=/export/home/jaap/.sage//tmp
SAGE64=yes
/export/home/jaap/Downloads/sage-4.3.1.alpha1
sage subshell$ env | grep FLAG
LDFLAGS=
FCFLAG64=-m64
SHARED_FLAG=-shared
CXXFLAGS= -Wall -g -m64
FCFLAGS= -Wall -g -m64
SONAME_FLAG=-soname
CFLAGS= -Wall -g -m64
WHOLE_ARCHIVE_FLAG=--whole-archive
NO_WHOLE_ARCHIVE_FLAG=--no-whole-archive
CXXFLAG64=-m64
FPIC_FLAG=-fPIC
CFLAG64=-m64

I understand that FLAGS are not so relevant while building mpir.


The same Open Solaris on Dave Kirkby's box:

Finished extraction
****************************************************
Host system
uname -a:
SunOS hawk 5.11 snv_111b i86pc i386 i86pc Solaris
****************************************************
****************************************************
CC Version
gcc -v
Using built-in specs.
Target: i386-pc-solaris2.11
Configured with: ../gcc-4.3.4/configure --prefix=/usr/local/gcc-4.3.4-GNU-assembler-Sun-linker --with-as=/usr/local/binutils-2.20/bin/as --with-ld=/usr/ccs/bin/ld --with-gmp=/usr/local --with-mpfr=/usr/local
Thread model: posix
gcc version 4.3.4 (GCC)
****************************************************
Building 64 bit Solaris version
checking build system type... nehalem-pc-solaris2.11
checking host system type... nehalem-pc-solaris2.11
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking ABI=64
checking compiler gcc  -Wall -g -m64 -Wall -g -m64 ... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out

The build seems to work.

Help needed! Bill?

Shall I open a trac ticket?

Jaap


-- 
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

Reply via email to