I recently installed Fedora Core 5 (64-bit) on a new multi-pro server (AMD Opteron chips) that my colleagues and I are planning to use for some of our research work. One of our preferred applications is Maple. We recently site licesned a netwrok version of Maple 10, and proceeded to start the process of installing it on our new machine. In advance, I googled 'Fedora 5' and 'Maple', and discovered that a lot of folks have had problems with the installer .bin becuase the installer tries to set the environment variable
Well, news flash for Maplesoft - more and more kernels no longer support this bakcwards compatability (including RHEL 5, and Fedora Core 5, and I'll guess Suse 10, and a lot of other distros using the 2.6.x kernel).
OK, smart folks figured out you can edit the installer .bin (which is a compiled script), and comment out the export LD_ASSUME_KERNEL lines.
Fine, did that - and Maple installed just fine - all the directories were created, binaries looked like the right size.
Great right? Editing .bin worked right?
Well, perhaps this is a viable trick for single-user Maple, but if you're installing a networked, multi-user version, hang on - you still need to load the license manager daemon.
You read the docs, and what do you find? On 64-bit Linux platforms, you *must* use LD_ASSUME_KERNEL=2.4.1. And, because the program that starts the daemon (lmgrd) isn't editable, you're "hosed".
In other words, Maple 10 network version cannot be used on *any* Linux distro that (i) uses 2.6.x kernel, and (ii) has deprecated LD_ASSUME_KERNEL=2.4.1. And this includes Redhat, which is a fairly big player in the Linux scene.
So, any comment (suggestion) from Maplesoft on what to do?