Dear Kevin, It is not clear from your convoluted log, but I suspect this is a 64-bit system and I have the same problem here, i.e. Comis does not work properly. Our 64-bit systems have i386 emulation and I have put statically linked ia32 versions of pawX11 and paw++ for them, which seem to work well.
I have spent some time looking at it but have not had the motivation to finish it. I believe to get the C part of Comis working I should start with the alpha_osf version and try to get round any Linux clashes. Regards, Ian On Fri, 23 Jun 2006, Kevin B. McCarty wrote: > Dear PAW fans and authors, > > If you have the time, please direct your attention to Debian bug #374978: > > http://bugs.debian.org/374978 > > and let me know if you have any comments. The basic problem (see the > last email of mine that went to that bug report) is that it is possible > for names of functions and COMMON blocks in system libraries to clash > with user variables in PAW and override them. Any suggestions for how > to fix this (other than the ugly workaround I suggested in that last > email of ignoring symbols named "x_" and "y_") would be welcome. > > PAW authors, please notice that the problem is a little more severe for > the Debian version of PAW (due to the existence of Cern libraries > compiled as dynamic libraries, meaning that there are more functions and > COMMON blocks available to clash with user variable names) but can also > be triggered with the statically linked PAW (I tested it to be sure). > > best regards, > > -- Ian McLaren | CERN/PH | CH-1211 | Geneva 23 | Switzerland Office: 32 R-B06 | E-mail: [EMAIL PROTECTED] Phone: +41-22-767-5010 | Fax: +41 22 76 70300 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
