I can comment on the python-gnutls issue. The problem is that the API
for gnutls has changed and is NOT backwards compatible with the
previous releases. Hence, python-gnutls will not work since it is
simply a package that wraps the gnutls library and those wrappings
were automatically generated by gcc-xml and py2xml. Below is the
email I got from the python-gnutls author about what needs to be done
to get python-gnutls to work.
--------------------------------------------------------
show details Jan 11 (12 days ago)
Reply
On Friday 11 January 2008, you wrote:
> Hi Dan,
> We've been using your python-gnutls wrappers for a while now for the
> SAGE [1] project with great success. However we'd like to update to
> the latest gnutls release (2.2.0 ATM) and I noticed that they've made
> quite a few changes to the OpenPGP parts which causes
> incompatibilities with the wrapper. Do you have any plans to update
> python-gnutls to work with gnutls-2.2.0?
I will when the distribution I use will have it packaged. Until then I
stick with what I have since there is no reason for me to upgrade.
Otherwise, openpgp is not really used, just made available. So unless you
actively use the low level openpgp functions yourself it should not be a
problem. Otherwise, you can regenerate the low level libraries yourself
to match the latest gnutls. You just have to install the code generator
from http://starship.python.net/crew/theller/ctypes/ (xml2py) and gcc-xml
With them you can run make clean; make before you run setup.py build to
regenerate the low level library files to match the latest gnutls header
files.
--
Dan
On Jan 23, 2008 2:26 AM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Jan 23, 11:06 am, Simon King <[EMAIL PROTECTED]> wrote:
> > Dear Michael
> >
> > On Jan 23, 1:30 am, mabshoff <[EMAIL PROTECTED]
> >
> > dortmund.de> wrote:
> > > On Jan 22, 11:34 pm, Simon King <[EMAIL PROTECTED]> wrote:
> > <snip>
> > > > I mean: saying "./sage -notebook", i got a lot of error messages and
> > > > eventually an "Unhandled SIGSEGV".
> >
> > > I can reproduce it.
> >
> > Slightly relieving for me :-)
> >
> > > A couple remarks:
> >
> > > a) import gnutls works for 2.10.1.alpah2
> > > b) python_gnutls in the way we ship it is outdated. There is a 1.1.4
> > > at the cheese shop which compiles fine. But it doesn't make a
> > > difference.
> > > c) We might just me missing the asn1 librariy, one which can be found
> > > atftp://ftp.gnutls.org/pub/gnutls/libtasn1/libtasn1-1.2.tar.gz
> >
> > So does it mean i only have to wait until 2.10.1.alpha2 is available?
> > Or may i have done something wrong when i installed gnutls (using
> > yast)?
>
> I downgraded to the last known working gnutls.spkg and that didn't fix
> the problem. So I am currently trying to figure out what exactly is
> wrong. William started revisiting various alternatives and it seems
> likely now that we might downgrade for 2.10.1 and revisit the issue
> again in 2.10.2, unless we come up with some alternative
> implementation.
>
> > <snip>
> >
> > > What JDK are you running?
> >
> > What is a JDK?
> >
> > > jmol seems to have problems with non-Sun
> > > ones, so installing that ought to solve your problem in case it isn't
> > > GNUTLS related.
> >
> > jmol had no problems with my machine so far. When i use sage-2.10 that
> > i obtained from building sage-2.8.6 and successive upgrade, plot3d-ing
> > works fine.
> >
> > And i don't know if it is GNUTLS related, because there was no error
> > message. Simply "S.show()" had the same visible effect as saying
> > "none".
>
> See the other thread in sage-devel :)
>
> > Cheers
> > Simon
>
> Cheers,
>
> Michael
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
