Build failure on 4.3.4.rc0: 32/64 bit issue?

2 views
Skip to first unread message

Kiran Kedlaya

unread,
Mar 18, 2010, 7:40:51 AM3/18/10
to sage-devel
Alert readers of sage-devel and sage-release may know that since
4.3.4.alpha0, I haven't been able to compile sage on my somewhat
eccentric Fedora 10 system. It's a 64-bit system with 64-bit compilers
and such under /usr/lib, but it's on a network with mostly 32-bit
machines and their compilers are also visible under /usr/local/lib.

I keep hitting a build error in gd, with a linking error for iconv). I
put up the last install log:

http://math.mit.edu/~kedlaya/sage-434rc0.log

and the libtool script from the gd build directory:

http://math.mit.edu/~kedlaya/libtool

The latter has the following odd feature which may be causing the
problem. When the libtool script defines sys_lib_search_path_spec, it
includes

/scratch/sage-4.3.4.rc0/local/lib/../lib64/

which does not exist, but it doesn't include

/scratch/sage-4.3.4.rc0/local/lib/

which is where libiconv.so is actually located. Is this a symptom of
32/64 confusion?

Kiran

Dima Pasechnik

unread,
Mar 18, 2010, 11:38:51 AM3/18/10
to sage-devel
Kiran,
it should be possible by simply setting PATH appropriately to make all
the
unwanted /usr/local stuff invisible.
Did you try doing this?
(assuming you use bash as the shell, you can do
> PATH=whatever_stuff_you_need
> export PATH )
A similar problem arises on MacOSX, when one has some extra things,
like fink, installed.
E.g. I have
$ echo $PATH
/usr/local/texlive/2007/bin/powerpc-darwin:/sw/bin:/sw/sbin:/usr/bin:/
bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/X11R6/bin

In order to build, successfully, Sage, I need to do something like

$ PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin
$ export PATH

and then proceed to build Sage (without quitting this shell, cause
then you'd get the unneeded parts of the PATH back)

HTH,
Dmitrii

Kiran Kedlaya

unread,
Mar 18, 2010, 5:14:47 PM3/18/10
to sage-devel
A good suggestion, but it doesn't help in this case. This may be a
Fedora issue rather than a 32/64 bit issue, since Jaap Spies had
similar trouble.

There seems to be a configuration issue. The spkg runs the config
script with the options
---
./configure --prefix=/scratch/sage-4.3.4.rc0/local --without-jpeg --
without-x --with-zlib=/scratch/sage-4.3.4.rc0/local --with-freetype=/
scratch/sage-4.3.4.rc0/local --without-xpm
---
If I remove the --with-freetype option, the build succeeds. Why that
is the case is completely beyond me!

Kiran

Dima Pasechnik

unread,
Mar 18, 2010, 10:25:18 PM3/18/10
to sage-devel
I tried to update to 4.3.4.rc0 on MacOSX 10.5 PPC (G4) It has built,
but then it won't start:
---------------------------------------------------------------------------
ImportError Traceback (most recent call
last)
[...]
/usr/local/src/sage/sage-4.3.4.rc0/local/lib/python2.6/site-packages/
sage/matrix/matrix_space.py in <module>()
38 import matrix_modn_sparse
39
---> 40 import matrix_mod2_dense
41 #import matrix_mod2_sparse

42

ImportError: dlopen(/usr/local/src/sage/sage-4.3.4.rc0/local/lib/
python2.6/site-packages/sage/matrix/matrix_mod2_dense.so, 2): Symbol
not found: _iconv_close
Referenced from: /usr/local/src/sage/sage-4.3.4.rc0/local/lib//libgd.
2.dylib
Expected in: /usr/local/src/sage/sage-4.3.4.rc0/local/lib//libiconv.
2.dylib

Error importing ipy_profile_sage - perhaps you should run %upgrade?
WARNING: Loading of ipy_profile_sage failed.

(reinstalling iconv-1.13.1.spkg does not help)

Reply all
Reply to author
Forward
0 new messages