Re: lesstif - Recompile for shared Xt has STATUS_ACCESS_VIOLATION

[Harold L Hunt II]

Brian,

My rebuild with --enable-shared didn't actually create a shared version 
of Xm; I got lots of warnings about unresolved symbols not being allowed 
in shared libraries.  This rebuild worked just the same as my previous 
build against the shared libXt: moving, menus, everything worked, but 
mwm.exe gives a STATUS_ACCESS_VIOLATION when you choose "Close" from a menu.

I also logged into one of my other machines and installed the static 
lesstif, ran mwm.exe, and confirmed that the STATUS_ACCESS_VIOLATION 
occurs even when mwm.exe is built against a static libXt.

So, looks like this was a pre-existing problem.  Therefore, it should 
probably not hold up the current release of a new lesstif build.  I 
might go ahead and make a release now that I know that it isn't causing 
the Close crash.

Harold