On Aug 24, 11:15 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
> On 8/24/07, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > On Aug 24, 7:18 pm, "David Joyner" <[EMAIL PROTECTED]> wrote:
>
> > Hello David,
>
> > > On 8/24/07, mabshoff <[EMAIL PROTECTED]> wrote:
>
> > > > I will add the needed bits to the trac ticket. Is there a test suite
> > > > for Lie I could/should run?
>
> > > In .../LiE/progs there are some test files.
>
> > I ran them all and none of them crashed/complained. test1 gave an
> > awful lot of output, but according to the shell Lie terminated with
> > exit status 0. Some from the perspective of Solaris there seem to be
> > no problems which is very good news for the Sage Solaris port, we have
> > enough unresolved issues as it is there :(. They are getting steadily
> > fewer, but if there is anybody out there with deep knowledge about the
> > NTL and gcc 4.2 on Solaris and likes weired linker failures please
> > speak up.
>
> > Is it worth it to give feedback back to the Lie people regarding
> > Solaris? A quick grep didn't turn up anything useful, but this is the
>
> Marc van Leeuwen ([EMAIL PROTECTED]) is the current
> maintainer. He seems very helpful and would probably appreciate
> feedback.
>
Great, I am CCing him so he can catch up :-). The specific thread in
the google group sage-devel can be accessed via
http://groups.google.com/group/sage-devel/t/bfa83514467cdfe6
Marc, the Sage people (specifically Mike Hansen) have started writing
a wrapper to call Lie from Sage. We (i.e. me) have also done some
build tests on some common and not so common platforms and found some
issues, mainly the need to link against curses or ncurses. You have
some info about building Lie on OSX at your website and I will
hopefully have some time tomorrow to test it out there.
The is also a small issue in or around Objectwrite that valgrind
exposed. Being unfamiliar with the code somebody more familiar with
the code base might fix it:
==22512== Syscall param write(buf) points to uninitialised byte(s)
==22512== at 0x31058BFA60: __write_nocancel (in /lib64/libc-2.5.so)
==22512== by 0x31058686D2: _IO_file_write@@GLIBC_2.2.5 (in /lib64/
libc-2.5.so)
==22512== by 0x31058685E5: _IO_do_write@@GLIBC_2.2.5 (in /lib64/
libc-2.5.so)
==22512== by 0x310586971F: _IO_file_close_it@@GLIBC_2.2.5 (in /
lib64/libc-2.5.so)
==22512== by 0x310585E249: fclose@@GLIBC_2.2.5 (in /lib64/
libc-2.5.so)
==22512== by 0x40565C: Objectwrite (in /tmp/Work2/LiE/Lie.exe)
==22512== by 0x41241E: vid_writestring_tex_grp_tex (in /tmp/Work2/
LiE/Lie.exe)
==22512== by 0x406325: eval_value (in /tmp/Work2/LiE/Lie.exe)
==22512== by 0x41346F: arg_sequence (in /tmp/Work2/LiE/Lie.exe)
==22512== by 0x406169: eval_value (in /tmp/Work2/LiE/Lie.exe)
==22512== by 0x40291D: yyparse (in /tmp/Work2/LiE/Lie.exe)
==22512== by 0x40764D: main (in /tmp/Work2/LiE/Lie.exe)
==22512== Address 0x4C0B00F is not stack'd, malloc'd or (recently)
free'd
I stuck all the info in the track ticket #489 at
http://sagetrac.org/sage_trac/ticket/489
- If you would like a trac account please contact William Stein.I
couldn't find an issue tracker for Lie, if you do have one please let
us know and I will file any new potential issues there.
Let me know if you need any additional info or feedback.
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
