AFNI Message Board

Dear AFNI users-

We are very pleased to announce that the new AFNI Message Board framework is up! Please join us at:

https://discuss.afni.nimh.nih.gov

Existing user accounts have been migrated, so returning users can login by requesting a password reset. New users can create accounts, as well, through a standard account creation process. Please note that these setup emails might initially go to spam folders (esp. for NIH users!), so please check those locations in the beginning.

The current Message Board discussion threads have been migrated to the new framework. The current Message Board will remain visible, but read-only, for a little while.

Sincerely, AFNI HQ

History of AFNI updates  

|
December 16, 2004 02:46PM
To expand on Rick's comments:

Having two copies of AFNI on the system is generally a recipe for trouble. You will end up running out-of-date programs, or (as in this case) trying to mix up-to-date plugins with out-of-date main afni program.

Here, the messages are showing you that the plugins are in directory /usr/local/afni/linux_glibc22/, but they were clearly compiled against an afni program other than the one you are using when you type "afni" (since the plugins are calling for functions in the main afni program that aren't being found, but I'm sure Rick put them there).

If you are willing to wait a little (or a lot, perhaps), you could do something like

find / -name afni -type f -print > alist.out

then the text file 'alist.out' will contain a list of all the places on your system that have a regular file named 'afni'. Warning: if you have a RAID mounted, or other very large disk, this could take hours, as it will search everything. Also, unless you execute this command as root, you'll get a lot of messages to the screen complaining about permission problems. You can ignore those, OR you can replace the '/' after 'find' with $PATH -- specifying to search only the path directories. In any case, you should only keep one version of AFNI in the path!!!!!!!
Subject Author Posted

"failed to open plugin..."

kevin desimone December 16, 2004 01:18PM

Re: "failed to open plugin..."

rick reynolds December 16, 2004 01:36PM

Re: "failed to open plugin..."

bob cox December 16, 2004 02:46PM

Re: "failed to open plugin..."

mark December 16, 2004 08:30PM

Re: "failed to open plugin..."

Kevin DeSimone December 20, 2004 03:59PM

Re: "failed to open plugin..."

rick reynolds December 20, 2004 04:14PM