AMIDE: Amide's a Medical Imaging Data Examiner

Note: old questions no longer relevant to the current release of AMIDE can be found here

Installation Issues

• I'm trying to install on Mac OS X 10.4. I've followed the directions, but I'm getting the following error message:

  my_macosx_computer:/Users/my_name my_name# amide
  dyld: Library not loaded: /sw/lib/libiconv.2.dylib
       Referenced from: /sw/bin/amide
       Reason: Incompatible library version: amide requires version 6.0.0
  or later, but libiconv.2.dylib provides version 5.0.0
  Trace/BPT trap
     

  This problem is caused by having an old version of fink on your computer. Try upgrading fink by running:

  fink selfupdate
     



• I've installed AMIDE, but the help menus don't seem to be giving any help. Also, when AMIDE starts up, it gives the following error message:

   
  GnomeUI-WARNING **: Could not open help topics file NULL
     

  This problem is usually caused by installing AMIDE in /usr/local instead of /usr. Current versions of the GNOME help browser only check in /usr/share/gnome/help for application help files. To fix this, you can either install AMIDE in /usr, or you can link the AMIDE help files in /usr/local/share/gnome/help to /usr/share/gnome/help with the following command (done as root):

  ln -s /usr/local/share/gnome/help/amide /usr/share/gnome/help/amide
     

Compilation Errors

• I've installed AMIDE from source, but it doesn't seem to have support for XMedCon/GSL/DCMTK/etc. when I run the program.

  First, double check that you've actually got the package in question installed on your computer. Second, check what the error messages where when you ran "./configure"; some helpful stuff will be print out by configure itself, and more useful information will be in the config.log file.

  The most common problems on Linux are:

  1. xmedcon-config and/or gsl-config are not in your PATH statement. Find where these executables are, and add them to your path. The following line will usually do the trick:

     export PATH=$PATH:/usr/local/bin:/usr/local/xmedcon/bin 

     Then rerun the configure script.
  
  
  2. Your system does not know the location of the libraries for the packages in question. Find where the libraries are, and add these directories to /etc/ld.so.conf. The directories you'll need to add are usually "/usr/local/xmedcon/lib" and "/usr/local/lib". Then run (as root) /sbin/ldconfig, and rerun the configure script.
  
  

Running Errors

• AMIDE crashes when generating an MPEG.

  This is most likely due to a problem with libfame. Libfame has a fair amount of assembly code optimized functions, and this ends up making it fairly finicky as to which version of gcc it's compiled with.

  The solution is to rebuild libfame with "--enable-mmx=no" passed to the configure script. This will disable the assembly code functions, and use the straight C code ones instead. I've actually never been able to compile a stable version of libfame without disabling mmx.



• When I start AMIDE, there is an error of "libmdc.so.1 cannot open shared object file: No such file or directory". Or alternatively libvolpack.so.1 may be the problem.

  This is most likely because the system doesn't know where to find this library. Check where the library is, and that the directory where the library residues is entered in /etc/ld.so.conf. If its not, you'll need to add the location to /etc/ld.so.conf, and run /sbin/ldconfig to tell it about the changes in ld.so.conf.



• On Mac OS X, staring up AMIDE fails with a "cannot open display" warning.

  You're probably trying to run AMIDE from Terminal.app instead of X11.app. AMIDE is an X11 application, meaning an X11 server needs to be running to accept the graphical display of AMIDE. On Mac OS X, the X11 server is called X11.app. Start up X11.app, then start an x-terminal within X11.app (Menu: Applications->Terminal), and then run AMIDE by typing "amide" at the x-terminal's command prompt.