10 More Discussions You Might Find Interesting
1. 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
2. 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
3. Programming
I have one C program which contains a function call.
I have been given some .so and .h files.
I want to know how to compile and link the c program with .so files.
I tried following:
$ gcc My_program.c libCommon.so
My_program.c: In function āmainā:
My_program.c:11: warning: parameter names... (3 Replies)
Discussion started by: junaid.nehvi
3 Replies
4. Programming
I am trying to set up the gnu multiple precision arithmetic library for some c++ programming I have to do.
I am using a system with mac osx 10.6.3 and do NOT have root user access.
I'm trying to use gmp 5.0.1.
Since I don't have root user access, I had to install to a different directory
Thus... (3 Replies)
Discussion started by: bluejayek
3 Replies
5. 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
6. AIX
Hi,
I have one library(libfoo.a) that is folder /home/xyz and my c program is in /home/xyz/cprog. Whenever I issue cc command
cc -o test test.c -lfoo , i get the error /usr/bin/ld: cannot find -lfoo.
echo $PATH has already listing of /home/xyz variable, even LIBPATH also has same entry... (0 Replies)
Discussion started by: rishisoft1
0 Replies
7. UNIX for Dummies Questions & Answers
Getting the following error ,
ld: /opt/syncsort39/lib/libsyncsort.sl: Mismatched ABI. 64-bit PA shared library found in 32-bit link.
Is there any difference in the ld options in opt file while linking a 64 bit shared library ? Or is the problem because we are trying to link both 32 bit and 64... (3 Replies)
Discussion started by: arunkumar_mca
3 Replies
8. Programming
hi all !
Do I need all the shared objects to be present while compiling my code which has reference to a only one shared object, which in turn refers to another shared object.
for example I want to compile example.c which refers to sample.so
sample.so has refrence to anothersample.so
do... (2 Replies)
Discussion started by: disclaimer
2 Replies
9. Programming
Hi
I'm getting
ld: fatal: option -h and building a dynamic executable are incompatible
ld: fatal: Flags processing errors
When I run
ld -shared -L/usr/dt/lib -lDtSvc -o builtin.so Workspace.o
after running
gcc -fPIC -I/usr/X11R6/include -I/usr/dt/include -c Workspace.c
I'm... (6 Replies)
Discussion started by: laho
6 Replies
10. Programming
I'm runtime linking (dlopen and dlsym) to a shared object (library) I've created and after a number of function calls into the library the program core dumps (Illegal operation). This only occurs during runtime linking. If I use the same library and dynamically link during compile time everything... (3 Replies)
Discussion started by: dneely
3 Replies
plock(2) System Calls Manual plock(2)
NAME
plock() - lock process, text, data, stack, or shared library in memory
SYNOPSIS
DESCRIPTION
The system call allows the calling process to lock the text segment of the process (text lock), its data segment (data lock), or both its
text and data segment (process lock) into memory. Stack segments are also locked when data segments are locked. Shared library text and
shared library data segments (shlib lock) can also be locked. Locked segments are immune to all routine swapping. also allows these seg-
ments to be unlocked.
The effective user ID of the calling process must be a user with the privilege.
op must be one of the following:
Lock text and data segments into memory (process lock)
Lock text segment into memory (text lock)
Lock data segment into memory (data lock)
Remove locks
Lock shared library text and shared library data segments (shared library lock)
Lock text, data and shared library text and shared library data segments
into memory (process and shared library lock)
Lock text, shared library text and shared library data segments into memory
(text and shared library lock)
Lock data, shared library text and shared library data segments into memory
(data and shared library lock)
Although and the family of functions may be used together in an application, each may affect the other in unexpected ways. This
practice is not recommended.
Security Restrictions
Some or all of the actions associated with this system call require the privilege. Processes owned by the superuser have this privilege.
Processes owned by other users may have this privilege, depending on system configuration. See privileges(5) for more information about
privileged access on systems that support fine-grained privileges.
RETURN VALUE
returns the following values:
Successful completion.
Failure.
The requested operation is not performed. is set to indicate the error.
ERRORS
If fails, is set to one of the following values.
op is equal to and a process lock, a text lock, or a data lock already exists on the calling process.
op is equal to and a text lock or process lock already exists on the calling process.
op is equal to and a data lock, or process lock already exists on the calling process.
op is equal to and no type of lock exists on the calling process.
op is equal to and there are no unlocked shared library segments in the calling process.
op is equal to and a process lock, a text lock, or a data lock already exists on the calling process.
op is equal to and a text lock or process lock already exists on the calling process.
op is equal to and a data lock, or process lock already exists on the calling process.
op is not equal to one of the values specified in
is not allowed in a
window. See vfork(2).
There is not enough lockable memory in the system
to satisfy the locking request.
The effective user ID of the calling process
is not a user with the privilege.
EXAMPLES
The following call to locks the calling process in memory:
SEE ALSO
setprivgrp(1M), exec(2), exit(2), fork(2), getprivgrp(2), mlock(2), vfork(2), privileges(5).
STANDARDS CONFORMANCE
plock(2)
