| Author |
Message
|
| mhubbard |
 Posted: Fri Oct 11, 2013 6:14 am Post subject: Missing shared libraries on 64 bit install (version 7.5) |
 |
|
Acolyte
Joined: 25 Aug 2004
Posts: 54
|
Hello - it has been a while.
I have downloaded both the i386 and the x86_64 versions of WMQ v 7.5 for Linux. My server is running i386 and has been built and is working beautifully. I can connect to it from a client box running a v6 32 bit client.
My next goal was to get that same client application recompiled and running on a fresh new 64 bit box using the 64 bit v7.5 client.
From the error logs on this new client box, I am seeing:
AMQ6174: The dynamically loadable shared library '/opt/mqm/lib64/amqcc62a_r' was not found. The system returned error number '2' and error message 'No such file or directory'.
Indeed - there is not libamqcc62a_r in that location on the client box.
Checking the Server box, I do find such a library at /opt/mqm/lib and discover that it was delivered by the MQSeriesRuntime rpm.
Using rpm2cpio MQSeriesRuntime-7.5.0-1.x86_64.rpm | cpio -imdv, I find that this library is not contained in the rpm at all, though doing the same for the i386 rpm shows that it is present there.
Any ideas?
Thank you
_________________
Michael J. Hubbard |
|
| Back to top |
|
 |
| markt |
| Posted: Fri Oct 11, 2013 6:22 am Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 508
|
| You're really using LU6.2 protocol for the channel? |
|
| Back to top |
|
|
| mhubbard |
| Posted: Fri Oct 11, 2013 7:24 am Post subject: |
|
|
Acolyte
Joined: 25 Aug 2004
Posts: 54
|
No - not at all. googling that library, I got the impression it was related to that - but I had no idea why it was being requested. .....maybe a missing channel table.....
_________________
Michael J. Hubbard |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Oct 11, 2013 7:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
what'd you use to compile the client app?
i.e. what was the full gcc/cc command? what was the link command, if separate? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Oct 11, 2013 7:29 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| mqjeff wrote: |
what'd you use to compile the client app?
i.e. what was the full gcc/cc command? what was the link command, if separate? |
Copy/paste the entire compile/bind script here.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mhubbard |
| Posted: Fri Oct 11, 2013 8:56 am Post subject: |
|
|
Acolyte
Joined: 25 Aug 2004
Posts: 54
|
Well it's a bit messy since our builds all use ant - but I was able to extract these commands:
g++ -g -O2 -Wall -D_REENTRANT -DGCCV4 -DDEBUG '-DHOSTNAME="${env.HOST}"' '-DUSER="mhubbard"' '-DOS_SYSNAME="${env.SYS}"' '-DCOMPILER="${env.COMPILER}"' -fPIC -c -I/app/manualbuildsdev/SWeetCode/trunk/rcmsCTP/include -I/app/manualbuildsdev/SWeetCode/trunk/rcmsCTP/include/sherlock/common/include -I/app/manualbuildsdev/SWeetCode/trunk/thirdparty/xerces-c-src_3_0_1 -I/app/manualbuildsdev/SWeetCode/trunk/thirdparty/xerces-c-src_3_0_1/xercesc -I/app/manualbuildsdev/SWeetCode/trunk/corelibs/frw/c/include -I/app/manualbuildsdev/SWeetCode/trunk/corelibs/ssl/c/include -I/app/manualbuildsdev/SWeetCode/trunk/corelibs/com/c/include -I/app/manualbuildsdev/SWeetCode/trunk/corelibs/net/c/include -I/app/manualbuildsdev/SWeetCode/trunk/corelibs/sys/c/include -I/app/manualbuildsdev/SWeetCode/trunk/corelibs/mq/c/include -I/app/manualbuildsdev/SWeetCode/trunk/thirdparty/mqm/inc64 -I/usr/include -I/usr/local/ssl/include -I/app/manualbuildsdev/SWeetCode/trunk /app/manualbuildsdev/SWeetCode/trunk/rcmsCTP/RCMSCTPAuthd/RCMSAuthServer.C /app/manualbuildsdev/SWeetCode/trunk/rcmsCTP/RCMSCTPAuthd/RCMSAuthd.C /app/manualbuildsdev/SWeetCode/trunk/rcmsCTP/RCMSCTPAuthd/RCMSAuthorizer.C /app/manualbuildsdev/SWeetCode/trunk/rcmsCTP/RCMSCTPAuthd/RCMSdbCommand.C
gcc -L/app/manualbuildsdev/SWeetCode/trunk/rcmsCTP/RCMSCTPAuthd/build/lib -L/home/mhubbard/CODE/SWeetCode/trunk/rcmsCTP/RCMSCTPAuthd/lib -L/app/manualbuildsdev/SWeetCode/trunk/rcmsCTP/RCMSCTPAuthd/build/lib -L/app/manualbuildsdev/SWeetCode/trunk/rcmsCTP/RCMSCTPAuthd/../../corelibs/lib -L/app/manualbuildsdev/SWeetCode/trunk/rcmsCTP/RCMSCTPAuthd/../../thirdparty/xerces-c-src_3_0_1/lib64 -L/app/manualbuildsdev/SWeetCode/trunk/rcmsCTP/RCMSCTPAuthd/../../thirdparty/mqm/lib64/4.1 -L/app/manualbuildsdev/SWeetCode/trunk/rcmsCTP/RCMSCTPAuthd/../../thirdparty/mqm/lib64 -L/app/manualbuildsdev/SWeetCode/trunk/rcmsCTP/RCMSCTPAuthd/../../rcmsCTP/lib/OPTIMIZE -Wl,-rpath,/app/manualbuildsdev/SWeetCode/trunk/rcmsCTP/RCMSCTPAuthd/lib,-rpath,/app/manualbuildsdev/SWeetCode/trunk/thirdparty/mqm/lib64 -o RCMSCTPAuthd ../DEBUG/RCMSAuthd.o ../DEBUG/RCMSAuthorizer.o ../DEBUG/RCMSAuthServer.o ../DEBUG/RCMSdbCommand.o -lsw-corelibs-frw -lsw-corelibs-ssl -lsw-corelibs-sys -lsw-corelibs-com -lsw-corelibs-mq -lsw-rcms-mq -lxerces-c -lssl -lc -limqb23gl_r -limqc23gl_r -lmqic_r -ldsg -lmysqlclient_r -lmysql -lschema-mysql -lsherlock
The mqm shared objects are in the thirdparty/mqm/lib64 dirs.
_________________
Michael J. Hubbard |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Oct 11, 2013 9:01 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If I'm reading this right,
| mhubbard wrote: |
| -I/app/manualbuildsdev/SWeetCode/trunk/corelibs/mq/c/include -I/app/manualbuildsdev/SWeetCode/trunk/thirdparty/mqm/inc64 |
You are doing a build against copies of the MQ library files that are actually checked into your source control, rather than against "real" install performed by an MQ installer at a known fixed level.
So I'd guess that your copy of the MQ includes is not up to date, likewise with the libs. |
|
| Back to top |
|
|
| mhubbard |
| Posted: Fri Oct 11, 2013 9:10 am Post subject: |
|
|
Acolyte
Joined: 25 Aug 2004
Posts: 54
|
I have found it! Sorry for wasting your time. It was a coding issue on my side that had this rather strange manifestation. I wasn't properly sending in the string defining my channel. Perhaps with no solid channel definition, the queue manager object wants to load all possibilities or something like that.
Thank you for trying to help me.
_________________
Michael J. Hubbard |
|
| Back to top |
|
|
|
|
