>The issue was in src/exec/Makefile where DX scavanges the lib dirs for .a >files
Yes, this needs to be fixed. If you look at http://opendx.watson.ibm.com/cgi-bin/dx/cvsweb/dx/src/exec/Makefile.am there's a bit of thrashing about on the issue. >The issue was in src/exec/Makefile where DX scavanges the lib dirs for .a >files Randall Hopper wrote: > Thanks David. Turns out that ImageMagick/convert works fine (it's > dynamically linked with all dependent packages via .so shared libraries). > The issue was in src/exec/Makefile where DX scavanges the lib dirs for .a > files (can't steal .o's from a .so), it picked up a version that was > mismatched from the header. Probably an admin problem here rather than a > fault in DX, but I haven't traced it through. > > Randy > > David Thompson: > |I typically choose the ImageMagick format to write out to and then > |you have to give it the proper extension in the file name. > |ImageMagick uses filenames similar to Windows to determine the > |appropriate type (they call them delegates). > | > |What I would do is make sure your ImageMagick is working correctly. > |Try converting a tiff with convert. If it is then try saving from the > |File... Save... menu in the image window and choose the ImageMagick > |pulldown and name the file with the .jpg extension. If this works, > |then its just a simple case of looking at the WriteImage module. > | > |David > | > |> Wrong JPEG library version: library is 61, caller expects 62 > |> child process 0 (110720) exited, status = 1 > > -- > Randall Hopper (mailto:[EMAIL PROTECTED]) > EPA Scientific Visualization Center > US EPA MD/24 ERC-1A; RTP, NC 27711
