95b was a small bugfix over 95 so I would guess the problem
was also present there.
Two of the changes in 0.93.95 appear important to you :
- build only 2.1, no more 1.2/2.0 version
- Fixes by Dave Williss for the (Microsoft) Windows platform.
One of the consequences is that the macro XMLIBEXPORT is used in
many places. On the Windows platform, we configure the build so
this means something to the compiler; on others it is blank.
The "Windows" platform Dave submitted fixes for is Windows with
the Microsoft compiler, so a different environment from yours.
Most of Dave's fixes were in the include files, adding XMLIBEXPORT.
The lib/Xm/Vendor.c was unchanged in the last couple of releases
so that looks like a wild goose chase to me.
Danny
On Tue, 2004-10-19 at 10:08, Harold L Hunt II wrote:
> New information:
>
> The first version that the problem appeared in was 0.93.95b.
>
> I modified one of the test programs to print a line at startup... the
> line is never printed, meaning that the error occurs during
> initialization of the program, specifically when the Xm library is being
> loaded. I #if 0'd the DllMain routine in Xm/Vendor.c to no avail; this
> confuses me because it is almost like saying that the library being
> generated is totally invalid and incapable of being loaded.
>
> This seems to have the potential to get interesting. I'm going to be
> doing some more testing, probably starting with the following:
>
> 1) Remove the -O3 flag and replace it with -O2, or even no optimization.
> See if problem persists.
>
> 2) Look into whether a base address was being passed to the linker in
> the 0.93.94 build... I noticed this during the later builds, but I don't
> recall if I saw it in earlier builds or not.
>
> Anywho, I've got some stuff to look into for a bit.
>
> Harold
>
> Harold L Hunt II wrote:
> > Hello there, this is Harold Hunt, LessTif maintainer for Cygwin.
> >
> > I have compiled LessTif 0.93.96 for Cygwin with minimal changes (thanks
> > for getting our last set of patches in back around March!). However,
> > applications that use LessTif are bombing on startup now with a status
> > access violation. I'm wondering if there were any changes that you can
> > think of, off hand, that might cause such problem on Cygwin. Please
> > remember that variables that are initialized to the address of something
> > (function, etc.) in another library cause problem for Cygwin (e.g.
> > vendor shell stuff). I doubt there were any changes like this, but
> > please let me know if there is anything that might seem suspicious.
> >
> > I'm monitoring this mailing list until I get this problem resolved.
> >
> > Harold
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Lesstif-discuss mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/lesstif-discuss
--
Danny Backx - danny.backx-at-planetinternet.be http://up.to/danny.backx
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Lesstif-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/lesstif-discuss
