Sage 3.3 build fails at "md5 module failed to import"

[Amir]

Got the following error:

make[2]: Leaving directory `/titan_home/uhm/khosra/sage-3.3/spkg/build/
python-2.5.2.p8/src'
Sleeping for three seconds before testing python
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usit/titan/u1/khosra/sage-3.3/local/lib/python2.5/md5.py",
line 6, in <module>
from hashlib import md5
File "/usit/titan/u1/khosra/sage-3.3/local/lib/python2.5/
hashlib.py", line 133, in <module>
md5 = __get_builtin_constructor('md5')
File "/usit/titan/u1/khosra/sage-3.3/local/lib/python2.5/
hashlib.py", line 60, in __get_builtin_constructor
import _md5
ImportError: No module named _md5
md5 module failed to import

As suggested in a previous sage-devel post, tried:

export MAKE="make -j1",

with the same error. Machine is a node of a heterogeneous cluster of
'Rocks' linux opteron and xeon machines.

I am trying to build sage from scratch as I get the following error
when starting sage using the ubuntu opteron build:

sage.bin: /lib64/tls/libc.so.6: version `GLIBC_2.4' not found
(required by sage.bin)
python: /lib64/tls/libc.so.6: version `GLIBC_2.4' not found (required
by python)
sage.bin: /lib64/tls/libc.so.6: version `GLIBC_2.4' not found
(required by sage.bin)

Given my little experience with building sage, I may have better luck
solving the second issue than the build from source issue. I think the
machine has glibc-2.3.4.

Thanks,
Amir.

[mabshoff]

On Feb 25, 12:30 pm, Amir <amirn...@gmail.com> wrote:
> Got the following error:

Hi Amir,

<SNIP>

> export MAKE="make -j1",
>
> with the same error. Machine is a node of a heterogeneous cluster of
> 'Rocks' linux opteron and xeon machines.

Ok, any chance you do not have any OpenSSL installed by the system?
Python relies on that for the md5 module to work.

> I am trying to build sage from scratch as I get the following error
> when starting sage using the ubuntu opteron build:
>
> sage.bin: /lib64/tls/libc.so.6: version `GLIBC_2.4' not found
> (required by sage.bin)
> python: /lib64/tls/libc.so.6: version `GLIBC_2.4' not found (required
> by python)
> sage.bin: /lib64/tls/libc.so.6: version `GLIBC_2.4' not found
> (required by sage.bin)
>
> Given my little experience with building sage, I may have better luck
> solving the second issue than the build from source issue. I think the
> machine has glibc-2.3.4.

Well, glibc 2.3.4 is not compiled with the same config options
everywhere, so in the end if you do not find a matching binary
compiling from sources is highly recommended. You tried that as you
mentioned about, so if it isn't an OpenSSL issue please compress
install.log and post a link here so I can take a look.

> Thanks,
> Amir.

Cheers,

Michael

[Amir]

Dear Michael,

On Feb 26, 2:31 am, mabshoff <mabsh...@googlemail.com> wrote:
> <SNIP>

>
> Well, glibc 2.3.4 is not compiled with the same config options
> everywhere, so in the end if you do not find a matching binary
> compiling from sources is highly recommended. You tried that as you
> mentioned about, so if it isn't an OpenSSL issue please compress
> install.log and post a link here so I can take a look.
>
> > Thanks,
> > Amir.
>
> Cheers,
>
> Michael

I double checked that openssl 0.9.8j was installed with libraries and
header files. I also checked that the native md5 python module worked.

install.log.gz is here:

http://www.mediafire.com/?sharekey=fc013eb7754c935b07258ee67c679e4ae04e75f6e8ebb871

The log seems to contain 2 of my make attempts after the first fail.

Thanks,
Amir.