Works fine. Thanks a lot!
*f*ck you Sun, without a good 64-bit jre.
To become root without setting root password, type this:
$ sudo su -m
-m to keep current user environment (ls color, path setting, etc)
Comment from: [Member]
Thank you for your suggestion but you must also consider that in order for it to work, the non-root user should be listed in the sudoers file; otherwise it will not work.
Comment from: Nobody [Visitor]
You gotta learn how to use yum bud…
#1) run yum ONCE for all the packages
yum install package1 package2 package3 …
** this is MUCH FASTER and won’t require the dangerous “-y” parameter.
#2) In your package list, do NOT include the version since the particular version you are using MAY NO LONGER BE AVAILABLE. Use “name.i386″, i.e. libXcomposite.i386 – yum knows quite well what to do with that and will select the newest version.
yum -y libXcomposite.i386
#3) You do NOT need to include DEPENDENCIES in the list. Yum will pick them up on its own.
Aside from that, your instructions seem to work.
Comment from: [Member]
Your comments are appreciated. A couple of points, though.
First, this is a hack, however ephemeral in (version) nature, it is a (relatively speaking) quick hack that worked for me when I faced the problem of not finding an appropriate package(s) for 64-bit Fedora 9 to run 32-bit applications, like the IBM Lotus Symphony of the subject.
The list of packages was compiled adhering closely to the GNU/Linux Debian existing ia32-libs equivalent package, using Fedora 9 native yum utility to figure out equivalents –including appropriate version numbers that you have noticed in the list. Evidently, due to time constraints, I could only weed out some (or most) dependencies in the list of packages; the few that remained I noticed that yum would graciously take care of.
Well, not being an expert yum user, but relying on input of more experienced users like yourself, the selected loop structure coupled with the provided list of packages are safe enough so as to use the -y option and spare the prospective user from agreeing to the package installations for every single instance of those.
One of the strengths of using any variety of GNU/Linux distributions, as opposed to closed source equivalent operating systems, is the flexibility that we as users are enabled (or empowered) with to achieve any given task using multiple approaches or methodologies. Accordingly, other prospective users who read your comment will be enlightened with an alternative to the procedure that I provided.
On the other hand, I am glad that the overall methodology and data list resource were useful you, nonetheless.
Comment from: Andrew Pearce [Visitor]
Thank you, this is a very powerful tutorial.
It works for more than just Symphony, I just managed to get CYCAS 39 working with it as well.
No more dual booting to 32bit linux for me.