10 More Discussions You Might Find Interesting
This is the first time that I created a dynamic library in linux and although the program works, I do not get the correct information about the library when executing ldd.
I explain the details:
1) Source code:
void bye (const char*... (9 Replies)
Discussion started by: jose_spain
Does anyone know whether it is possible to make self contained shared libraries ? (.so files). If so, what is the way to do it ?
---------- Post updated at 08:03 AM ---------- Previous update was at 07:56 AM ----------
On Solaris that is. (6 Replies)
Discussion started by: lkb
3. Red Hat
while running the below query it gives the shared libraries prmblem,
$ cd /oracle/app/product/fmw/asinst_1/bin/
$ ./opmnctl status
/oracle/app/product/fmw/Oracle_IDM1/opmn/bin/opmn: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: Permission... (0 Replies)
Discussion started by: rahulsword
I have a problem about loaded shared libraries. I'm issuing ‘procldd' for a process and AIX shows me the loaded shared libraries. I'm collecting these libraries and counting their size. They were 350MB. After this, I'm issuing ‘ps vx' and I'm seeing that the process takes 130MB from AIX's... (1 Reply)
Discussion started by: jhatzics
Please tell me how to manage the shared library on solaris 10!
which file to configure the library path?
which environment variable contains these paths ?
how to define the new library path?
thanks all! (2 Replies)
Discussion started by: quyetbm
6. UNIX for Advanced & Expert Users
I am trying to create a shared library from a .c file using
gcc -c -fpic -I/usr/local/include Chksum.C -o Chksum.o
gcc -shared -o libtclcksum.so Chksum.o
when i try to load this shared library libtclcksum.so in tclsh
% load libtclcksum.so
I get the following error:
couldn't load... (1 Reply)
Discussion started by: archana485
7. UNIX for Advanced & Expert Users
can someone explain whether my understanding is correct
lets suppose we have a program that uses library x.
if x is static then the code of x will be part of our program, so if we're going to have 5 executables of our program, then each executable will have x as part of it.
Also, x does not... (2 Replies)
Discussion started by: JamesByars
How do i make a library shared
say i have a library a.so which i have just compiled.
I want to make it shared how do i make it
Next Queation is what is the difference between a.so.0 a.so.1 a.so.2 & a.so :rolleyes: (1 Reply)
Discussion started by: wojtyla
9. UNIX for Dummies Questions & Answers
I have a doubt about the shared libraries. Where do you set the path for the shared libaries, for the dynamic loader to locate. Any suggestion would be of great help. thanks (3 Replies)
Discussion started by: ramkumar_gr
I am compiling code which produces .a and .la libraries. How can I produce .so libraries? I know that gcc -shared does but how? (2 Replies)
Discussion started by: thalex
LIBBASH(7) libbash Manual LIBBASH(7)
libbash -- A bash shared libraries package.
libbash is a package that enables bash dynamic-like shared libraries. Actually its a tool for managing bash scripts whose functions you may
want to load and use in scripts of your own.
It contains a 'dynamic loader' for the shared libraries ( ldbash(1)), a configuration tool (ldbashconfig(8)), and some libraries.
Using ldbash(1) you are able to load loadable bash libraries, such as getopts(1) and hashstash(1). A bash shared library that can be loaded
ldbash(1) must answer 4 requirments:
1. It must be installed in $LIBBASH_PREFIX/lib/bash (default is /usr/lib/bash).
2. It must contain a line that begins with '#EXPORT='. That line will contain (after the '=') a list of functions that the library
exports. I.e. all the function that will be usable after loading that library will be listed in that line.
3. It must contain a line that begins with '#REQUIRE='. That line will contain (after the '=') a list of bash libraries that are
required for our library. I.e. every bash library that is in use in our bash library must be listed there.
4. The library must be listed (For more information, see ldbashconfig(8)).
Basic guidelines for writing library of your own:
1. Be aware, that your library will be actually sourced. So, basically, it should contain (i.e define) only functions.
2. Try to declare all variables intended for internal use as local.
3. Global variables and functions that are intended for internal use (i.e are not defined in '#EXPORT=') should begin with:
For example, internal function myfoosort of hashstash library should be named as
This helps to avoid conflicts in global name space when using libraries that come from different vendors.
4. See html manual for full version of this guide.
Hai Zaar <firstname.lastname@example.org>
Gil Ran <email@example.com>
ldbash(1), ldbashconfig(8), getopts(1), hashstash(1) colors(1) messages(1) urlcoding(1) locks(1)
Linux Epoch Linux