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