11-01-2007
You say HPUX 11, but running on what?
There are basically five different runtimes, as follows....
CPU width Packaging
PA-RISC1.1, 32 bit mode, SOM
PA-RISC2.0, 32 bit mode, SOM
PA-RISC2.0, 64 bit mode, ELF
Itanium-2, 32 bit mode, ELF
Itanium-2, 64 bit mode, ELF
The immediate giveaway is if the library is of the form
"lib*.so[.major[.minor]]"
then it's ELF, if it's
"lib*.sl" or "lib*.major[.minor]"
then it's PA-RISC, if it's 32 bit then it's SOM.
You can only link like with like.
Last edited by porter; 11-14-2007 at 05:56 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. UNIX for Advanced & Expert Users
What is the primary difference between static library and dynamic library?
and how to write static shared library? (1 Reply)
Discussion started by: areef4u
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
Is there any way in C to access a function in C shared library.
I have used dlopen to access /load the c shared library but unable to
use the function in the shared object.
Thanks in advance :b: (1 Reply)
Discussion started by: yhacks
1 Replies
5. 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
6. 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
7. Programming
I'm having trouble with my makefile, I'm trying to code a shared library to be used by another program
*EDIT* Found the solution:
CC = g++
MODULES= readconfig.o ReadConfigLib.o
OBJECTS=
RCLOBJECTS= ReadConfigLib.cpp readconfig.cpp configDefinitions.h readconfig.h ReadConfigLib.h... (0 Replies)
Discussion started by: james2432
0 Replies
8. Solaris
We are trying to install our project on solaris 10 x86 machine. we are getting the following error.
Can't load '/u01/apps/WatchMark/FlexPM//R39FOA1/sw/perl/lib/auto/DBI/DBI.so' for module DBI: ld.so.1: perl: fatal:
/u01/apps/WatchMark/FlexPM//R39FOA1/sw/perl/lib/auto/DBI/DBI.so: wrong ELF data... (3 Replies)
Discussion started by: Jagandadi
3 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 FREEBSD
elf_cntl
ELF_CNTL(3) BSD Library Functions Manual ELF_CNTL(3)
NAME
elf_cntl -- control an elf file descriptor
LIBRARY
ELF Access Library (libelf, -lelf)
SYNOPSIS
#include <libelf.h>
int
elf_cntl(Elf *elf, Elf_Cmd cmd);
DESCRIPTION
Function elf_cntl() controls the ELF library's subsequent use of the file descriptor used to create ELF descriptor elf.
Argument cmd informs the library of the action to be taken:
ELF_C_FDDONE This value instructs the ELF library not to perform any further I/O on the file descriptor associated with argument elf. For
ELF descriptors opened with mode ELF_C_WRITE or ELF_C_RDWR subsequent elf_update() operations on the descriptor will fail.
ELF_C_FDREAD This value instructs the ELF library to read in all necessary data associated with ELF descriptor elf into memory so that the
underlying file descriptor can be safely closed with command ELF_C_FDDONE.
Argument elf must be an ELF descriptor associated with a file system object (e.g., an ar(1) archive, an ELF file, or other data file).
IMPLEMENTATION NOTES
Due to use of mmap(2) internally, this function is a no-op for ELF objects opened in ELF_C_READ mode.
RETURN VALUES
Function elf_cntl() returns 0 on success, or -1 if an error was detected.
ERRORS
[ELF_E_ARCHIVE] Argument elf is a descriptor for an archive member.
[ELF_E_ARGUMENT] Argument elf was NULL.
[ELF_E_ARGUMENT] Argument cmd was not recognized.
[ELF_E_MODE] An ELF_C_FDREAD operation was requested on an ELF descriptor opened for writing.
SEE ALSO
elf(3), elf_begin(3), elf_end(3), elf_next(3), elf_update(3), gelf(3)
BSD
August 9, 2006 BSD