On 2009-Jul-27 20:41:04 +1000, Minh Nguyen <nguyenmi...@gmail.com> wrote:
>As of Sage 4.1.1.alpha1, the compilation of Sage now dies when it
>comes to compiling MPIR. The full log is up at

Hmmm...  sage-4.1 on FreeBSD/i386 got past that point.

>g++ -shared -nostdlib /usr/lib/crti.o /usr/lib/crtbeginS.o  .libs/dummy.o 
>cxx/.libs/isfuns.o cxx/.libs/ismpf.o cxx/.libs/ismpq.o cxx/.libs/ismpz.o 
>cxx/.libs/ismpznw.o cxx/.libs/osdoprnti.o cxx/.libs/osfuns.o cxx/.libs/osmpf.o 
>cxx/.libs/osmpq.o cxx/.libs/osmpz.o  -Wl,--rpath 
>-Wl,/usr/scratch/mvngu/sage-4.1.1.alpha1/local/lib 
>-L/usr/scratch/mvngu/sage-4.1.1.alpha1/local/lib -lgmp -L/usr/lib -lstdc++ -lm 
>-lc -lgcc_s /usr/lib/crtendS.o /usr/lib/crtn.o  -m64 -march=k8 -mtune=k8 
>-Wl,-soname -Wl,libgmpxx.so.4 -o .libs/libgmpxx.so.4
>/usr/bin/ld: cannot find -lgmp
>libtool: install: error: relink `libgmpxx.la' with the above command before 
>installing it

This looks like a bug somewhere.  The equivalent command line from my
sage-4.1 build on freebsd32 follows.  Note that it's linking libgmp
from within the build tree, rather than the not-yet-installed
sage/local/lib.  I don't have any local patch for mpir-1.2.p4 so I'm
not sure what might have caused it.

g++ -shared -nostdlib /usr/lib/crti.o 
/usr/local/lib/gcc43/gcc/i386-portbld-freebsd7.2/4.3.4/crtbeginS.o  
.libs/dummy.o cxx/.libs/isfuns.o cxx/.libs/ismpf.o cxx/.libs/ismpq.o 
cxx/.libs/ismpz.o cxx/.libs/ismpznw.o cxx/.libs/osdoprnti.o cxx/.libs/osfuns.o 
cxx/.libs/osmpf.o cxx/.libs/osmpq.o cxx/.libs/osmpz.o  -Wl,--rpath 
-Wl,/usr/home/peter/sage-4.1/spkg/build/mpir-1.2.p4/src/.libs -Wl,--rpath 
-Wl,/usr/home/peter/sage-4.1/local/lib ./.libs/libgmp.so 
-L/usr/home/peter/sage-4.1/local/lib 
-L/usr/local/lib/gcc43/gcc/i386-portbld-freebsd7.2/4.3.4 
-L/usr/local/lib/gcc43/gcc/i386-portbld-freebsd7.2/4.3.4/../../.. -lstdc++ -lm 
-lgcc_s /usr/local/lib/gcc43/gcc/i386-portbld-freebsd7.2/4.3.4/crtendS.o 
/usr/lib/crtn.o  -m32 -mtune=core2 -march=core2 -Wl,-soname -Wl,libgmpxx.so.4 
-o .libs/libgmpxx.so.4

On 2009-Jul-27 18:28:02 -0700, jmakov <jernej.makov...@gmail.com> wrote:
>If FBSD support is in the clouds couldn`t sage be compiled on linux
>(could be virtualized on FBSD) and then run on FBSD as a linux binary?
>Are there any problems when running as linux binary? FBSD 8.0 should
>have 2.6 kernel support ready...

Note that FreeBSD support for 64-bit Linux doesn't exist yet - though
you can run 32-bit x86 Linux apps on both FreeBSD/i386 and FreeBSD/amd64.

I've have a (very) quick go at making several sage-4.0.2 run on
FreeBSD 8.x (ie Linux 2.6) without a great deal of success.  I expect
it could be done but isn't as simple as installing linux_base-f10 and
unpacking sage.  (Unfortunately, I can't find the notes I made, hence
my vagueness).

At this stage, I'd prefer to expend effort on native support for
FreeBSD.  From the FreeBSD point of view, this (potentially) provides
support across more platforms.  From the Sage point of view, it
improves portability.

-- 
Peter Jeremy

Attachment: pgpd86s8L84pl.pgp
Description: PGP signature

Reply via email to