nirgrahamuk:
lhunsicker declared that they had the 32bit binaries, but didnt explain how they came to that understanding.
When this issue arose a few days ago, I attempted to update the package ctsem. The update completed for the 32-bit version, but then failed for the 64 bit version. As you may know, the ctsem install from source generates miles of text. So to try to find the failure point, I tried installing ctsem with the 'INSTALL_opts = '--no-multiarch' option. That installed the 32-bit version of the update with no problems, but didn't try to install the 64-bit version.
In any case, this AM the ctsem update from source worked without a hitch. I think that there is something inconsistent in the way our cluster accesses user files. Sometimes my .libPaths() lists my personal library directly, and sometimes it seems to be a subdirectory of the system recycle bin. I suspect when a package install from source fails, .libPaths() lists the recycle bin subdirectory. This aliasing may well screw up the install. I have to have a few more examples of this issue. If I confirm it, I'll discuss this with our sysop.
Thanks all for your comments.