It is impossible (or at least very, very hard) to link -32 and -n32 libraries as ld checks this. I doubt that is the cause of your problem.
> -----Original Message----- > From: Jeff Braun [SMTP:[EMAIL PROTECTED] > Sent: Thursday, 15 June 2000 6:50 > To: [email protected] > Subject: [opendx-dev] SGI Image Magick 5.2 - FreeMemory > > I still can not save Image Magick supported formats using 5.2. I have > debugged the problem to FreeMemory() in TemporaryFilename. I can not seem > to step through FreeMemory. I commented out FreeMemory to see what would > happen and then I get another error at the next FreeMemory at the end of > DestroyImage (line 2201 in image.c) called by SetImageInfo (from > ReadImage). > > At FreeMemory, it appears to be accessing memory.c line 243 in libdx with > garbage about flist, not FreeMemory on line 121 of magick/memory.c. Would > order of libraries matter or should I try renaming libdx/memory.c to say > dxmemory.c? > > I think everything is -n32, but could that be a source of the problem if > somewhere an o32 library is being used? > > Anyone have DX working from CVS with IM 5.2 on an SGI? > > I am headed out of town, so I will not be able to look into this further > until Monday. > > Jeff > >
