|
|
Sponsored Content
Operating Systems
AIX
convert 32 bit shared library to 64bit
Post 302474276 by frank_rizzo on Tuesday 23rd of November 2010 10:50:57 PM
|
|
10 More Discussions You Might Find Interesting
1. Programming
hello all
I want to work in shared libraries how can i work in
Linux Environment ? (2 Replies)
Discussion started by: rajashekaran
2 Replies
2. Programming
I generated my shared library in 64bit on AIX, but when I ran ldd, it says:
Could not load program libmylib.so:
Could not load module libmylib.so.
The module has an invalid magic number.
Anyone knows how to list library dependencies with 64bit shared library on AIX?
If you... (1 Reply)
Discussion started by: modemer
1 Replies
3. Programming
I need to create a shared library to access an in memory DB. The DB is not huge, but big enough to make it cumbersome to carry around in every single process using the shared library. Luckily, it is pretty static information, so I don't need to worry much about synchronizing the data between... (12 Replies)
Discussion started by: DreamWarrior
12 Replies
4. Programming
I am writing a shared library in Linux (but compatible with other UNIXes) and I want to allow multiple instances to share a piece of memory -- 1 byte is enough. What's the "best" way to do this? I want to optimize for speed and portability.
Obviously, I'll have to worry about mutual exclusion. (0 Replies)
Discussion started by: otheus
0 Replies
5. UNIX for Advanced & Expert Users
I have one app binary 'main' which is dependent on shared object libfoo.so
owner of main and libfoo.so is user 'oracle:dba'
> ldd main
libfoo.so => ./libfoo.so
libCstd.so.1 => /usr/lib/libCstd.so.1
libCrun.so.1 => /usr/lib/libCrun.so.1
libm.so.2 => ... (1 Reply)
Discussion started by: vpatil
1 Replies
6. Programming
I have one app binary 'main' which is dependent on shared object libfoo.so
owner of main and libfoo.so is user 'oracle:dba'
> ldd main
libfoo.so => ./libfoo.so
libCstd.so.1 => /usr/lib/libCstd.so.1
libCrun.so.1 => /usr/lib/libCrun.so.1
libm.so.2 => ... (1 Reply)
Discussion started by: vpatil
1 Replies
7. Shell Programming and Scripting
Hi:
I have a library that it only offers Makefile for building static library. It built libxxx.a file. How do I in any way build a shared library? (either changin the Makefile or direct script or command to build shared library)
Thanks. (1 Reply)
Discussion started by: cpthk
1 Replies
8. HP-UX
We are facing issue with shared library file, we are getting difference in content for same shared file for chatr command :confused: , below are the detail about *.sl file, even we are also getting difference in size of both file. can you please tell me what will be the issue for same. is my new... (1 Reply)
Discussion started by: amodkavi
1 Replies
9. Programming
Hello.
I am new to this forum and I would like to ask for advice about low level POSIX programming.
I have to implement a POSIX compliant C shared library.
A file will have some variables and the shared library will have some functions which need those variables.
There is one special... (5 Replies)
Discussion started by: iamjag
5 Replies
10. AIX
I'm trying to install libiconv to AIX 7.1 from an rpm off of the perzl site. The rpm appears to install but I get this error message.
add shr4.o shared members from /usr/lib/libiconv.a to /opt/freeware/lib/libiconv.a
add shr.o shared members from /usr/lib/libiconv.a to ... (5 Replies)
Discussion started by: kneemoe
5 Replies
LEARN ABOUT NETBSD
compat_netbsd32
COMPAT_NETBSD32(8) BSD System Manager's Manual COMPAT_NETBSD32(8) NAME
compat_netbsd32 -- setup procedure for 32-bit compatibility on 64-bit platforms DESCRIPTION
The compat_netbsd32 module allows NetBSD/sparc64 to run NetBSD/sparc executables, and NetBSD/amd64 to run NetBSD/i386 executables. To use compat_netbsd32, one must either have COMPAT_NETBSD32 and EXEC_ELF32 in the kernel, or load the compat_netbsd32 and exec_netbsd32 ker- nel modules. Static executables typically need no additional setup. Dynamic binaries require the dynamic linker plus shared libraries. Most of these files will need to be placed under /emul/netbsd32. The easiest method of installing support for these is via the emulators/netbsd32_compat14, emulators/netbsd32_compat15, and emulators/netbsd32_compat16 packages, provided in the NetBSD packages collection. These install 32-bit a.out and ELF compatibility libraries, respectively. The details of what is actually necessary for correct operation are given below. This obviously is handled by the emulator packages. For a.out compatibility, /usr/libexec/ld.so from a 32-bit distribution is required to exist as /emul/netbsd32/usr/libexec/ld.so. For 32-bit ELF compatibility, /usr/libexec/ld.elf_so needs to be in /emul/netbsd32/usr/libexec/ld.elf_so. The shared libraries for a.out binaries do not live under the /emul/netbsd32 directory, but under the /emul/aout directory, where the a.out dynamic linker will find them. BUGS
A list of things which fail to work in compatibility mode should be here. IPC is not well supported. sysctl(3) is not well supported. BSD
March 11, 2006 BSD