On Feb 11, 7:40 am, gedaliah <gwol...@gmail.com> wrote:
> On Feb 10, 4:48 pm, mabshoff <mabsh...@googlemail.com> wrote:
> <SNIP>
Hi,
> > Keep me in the loop about any other problems you see. If the gnutls
> > problem is the only one preventing us from building on RHEL 4.7 this
> > should be trivial to fix to add official support for RHEL 4.
>
> Got past atlas -- fails for singular. Gzipped install log can be
> downloadedhttp://web.njit.edu/~gwolosh/install.log.gz.
This one puzzles me since it basically all goes well until the final
linking stage:
g++ -I. -I../kernel -I/afs/cad/u/g/w/gwolosh/ftp/linux/sage/
sage-3.2.3/local/include -I. -I../kernel -I/afs/cad/u/g/w/gwolosh/ftp/
linux/sage/sage-3.2.3/local/include
-I/afs/cad/u/g/w/gwolosh/ftp/linux/sage/sage-3.2.3/local/include -I/
afs/cad/u/g/w/gwolosh/ftp/linux/sage/sage-3.2.3/local/include -
DSTANDALONE_PARSER -o libparse li
bparse_main.o utils.o ../kernel/fegetopt.o -L/afs/cad/u/g/w/gwolosh/
ftp/linux/sage/sage-3.2.3/local/lib -ldl -rdynamic -L../kernel -
lkernel -L/afs/cad/u/g/w/gwolosh/f
tp/linux/sage/sage-3.2.3/local/lib -L/afs/cad/u/g/w/gwolosh/ftp/linux/
sage/sage-3.2.3/local/lib -lomalloc_ndebug
../kernel/libkernel.a(mmstd.o)(.text+0x76): In function `calloc':
/afs/cad/u/g/w/gwolosh/ftp/linux/sage/sage-3.2.3/local/include/
omalloc.c:32: undefined reference to `omMarkAsStaticAddr'
../kernel/libkernel.a(mmstd.o)(.text+0xa0):/afs/cad/u/g/w/gwolosh/ftp/
linux/sage/sage-3.2.3/local/include/omalloc.c:32: undefined reference
to `omMarkAsStaticAddr'
../kernel/libkernel.a(mmstd.o)(.text+0xe9): In function `malloc':
/afs/cad/u/g/w/gwolosh/ftp/linux/sage/sage-3.2.3/local/include/
omalloc.c:42: undefined reference to `omMarkAsStaticAddr'
../kernel/libkernel.a(mmstd.o)(.text+0x113):/afs/cad/u/g/w/gwolosh/ftp/
linux/sage/sage-3.2.3/local/include/omalloc.c:42: undefined reference
to `omMarkAsStaticAddr'
../kernel/libkernel.a(mmstd.o)(.text+0x3f6): In function `realloc':
/afs/cad/u/g/w/gwolosh/ftp/linux/sage/sage-3.2.3/local/include/
omalloc.c:77: undefined reference to `omMarkAsStaticAddr'
../kernel/libkernel.a(mmstd.o)(.text+0x4d6):/afs/cad/u/g/w/gwolosh/ftp/
linux/sage/sage-3.2.3/local/include/omalloc.c:99: more undefined
references to `omMarkAsStaticA
ddr' follow
../kernel/libkernel.a(mmstd.o)(.text+0x50d): In function `freeSize':
/afs/cad/u/g/w/gwolosh/ftp/linux/sage/sage-3.2.3/local/include/
omalloc.c:107: undefined reference to `_omDebugFree'
collect2: ld returned 1 exit status
make[4]: *** [libparse] Error 1
make[4]: Leaving directory `/afs/cad.njit.edu/u/g/w/gwolosh/ftp/linux/
sage/sage-3.2.3/spkg/build/singular-3-0-4-4-20080711.p2/src/Singular'
make[3]: *** [install] Error 1
make[3]: Leaving directory `/afs/cad.njit.edu/u/g/w/gwolosh/ftp/linux/
sage/sage-3.2.3/spkg/build/singular-3-0-4-4-20080711.p2/src'
make[2]: *** [/afs/cad/u/g/w/gwolosh/ftp/linux/sage/sage-3.2.3/local/
bin/Singular-3-0-4] Error 2
make[2]: Leaving directory `/afs/cad.njit.edu/u/g/w/gwolosh/ftp/linux/
sage/sage-3.2.3/spkg/build/singular-3-0-4-4-20080711.p2/src'
Unable to build Singular.
There are some other odd things in the logs, i.e compile warnings I
have never seen in that form before for Singular. Since the Singular
build is about 4000 lines of log this might take some time to figure
out.
In the past we have seen strange things happen on afs. I don't want to
point my finger at it, but would it be possible to build Sage in /tmp
on such a box? If it isn't that I would guess I need to break out my
RHEL 4.7 VMWare image and try to debug this.
If you don't hear back from me in the next couple days just bump the
thread.
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
