I was assuming that the problem was that Bruce did not know that he
could have the 32-bit and
64-bit perl modules loaded at the same time. I was just trying to
explain some of the considerations
of loading vendor supplied 32-bit and 64-bit modules. And getting the
loaded to load the right
one at the right time.
Ron
John Summerfield wrote:
Ron Foster at Baldor-IS wrote:
Bruce,
I have had a little experience getting 32 bit modules working on 64 bit
systems. In most cases, there are 32 bit versions in addition to the 64
bit versions of modules. And they can co-exist with the 64 bit versions
without too much trouble.
When you loaded your system did you check the box for 32 bit runtime
environment? In my experience this gets you both the 64 bit versions
and the 32 bit versions of the modules.
Once you do that, run ldconfig to get the loader cache set up properly.
If the configuration files are set up properly, the loader will look to
see if a 32 bit program is calling the module. If so, then it loads the
32 bit version of the module. If a 64-bit program is calling the
module, the 64 bit version gets loaded.
It works for modules in libraries that are listed in /etc/ld.so.conf.
Our application used DB2 connect. It's libraries were not in
ld.so.conf, so we had to play with PATH statements to get the proper
version loaded.
When you do a man on ldconfig, it does not sound like that is what it
will do (that is be a traffic cop between 32 bit and 64 bit modules).
The relevant sentence is : "ldconfig will attempt to deduce the type of
ELF libs (i.e., libc5 or libc6/glibc) based on what C libs, if any, the
library was linked against."
Then when you look at the /etc/ld.so.conf, you see that for certain
directories you see both 64 bit and 32 bit libs. It starts to make
sense what is happening.
Hope this helps,
Ron
On 12/11/2008 at 1:58 PM, <bruce.light...@its.ms.gov> wrote:
We ( rookies ) are trying to get an application installed on SLES 10.2
under VM for a trial - and hopefully production - but are having
troubles
of the niggling kind. Such as some of modules being ornery about
executing. Appears that the thing wants 32-bit perl whereas we have
64-bit
installed. Yast pulls down some "stuff" but we dont seem to get a
31/32 bit
executable for the module.
The application was "given" to us to pilot and currently runs on RHEL on
Intel - we will have to be able to put it on z/VM & either RHEL or
SLES to
be able to afford to run this "free" software.
In my experience, most application code doesn't care a lot whether it's
64-bit or 32-bit or 31-bit, just so long as it can count far enough with
big numbers.
I presume, Bruce, that you have the source code and have built it.
Running Intellish binaries on Zeds will never work.
Do check that the build process is producing 64-bit Z-code. That should
be the easiest option for getting a positive result.
I would not be at all enthusiastic about installing 31-bit Perl on my
64-it Linux.
It's probably worth installing the appropriate 64-bit (and maybe 32-bit)
CentOS release on a 64-bit peecee, just so you can learn how it's done.
CentOS is near enough RHEL for most purposes, so your initial test
environment would match the supplier's. Once you have it working on the
peecee you should know enough to make a sensible effort on SLES.
Note that you can get RHEL and SLES for evaluation on your Intellish
machines, and it's possible to have both installed at the same time - at
one time I had betas of RHEL5 AS and WS, Fedora Core 6, Opensuse 10 and
(I think) SLES10 beta on one system in a multiboot setup.
--
Cheers
John
-- spambait
1aaaa...@coco.merseine.nu z1aaaa...@coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
