Add shared members from library to same library in a different directory
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.
Code:
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 /opt/freeware/lib/libiconv.a
add shr4_64.o shared members from /usr/lib/libiconv.a to /opt/freeware/lib/libiconv.a
How do I go about adding these shared members to the /opt/freeware/lib/libiconv.a?
Edit: my first thought is to link the two using ln as below, but I would appreciate anyone's input.
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)
Hello,
On a Centos 5.0 box, I have two versions of a library (sqlite):
(1) in /usr/lib that was installed using yum (maybe from php but I am not really sure)
(2) in /usr/local/lib that I installed myself by compiling from the source code.
My C++ program contains the following lines:
... (12 Replies)
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)
I have never seen this issue before, but here is what is happening. I link an executable against two dynamic mlib libraries veclib and lapack. We place a newer version of these libraries in a write only directory and point the shlib_path at that directory. When the executable runs, it gets a... (3 Replies)
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)
I'm trying to get Valgrind to work with an openmpi application in OS X. However I want to hardcode the path to a shared library called libmpiwrap-amd64-darwin.so into my application so that it is available at runtime. In Linux this is relatively simple, I would just add the option... (0 Replies)
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)
Hi All,
i am facing shared library error, below is the output of the command I am executing on my client
# /usr/software/bin/sudo
/usr/software/bin/sudo: error while loading shared libraries: libaudit.so.1: cannot open shared object file: No such file or directory
#
I tried install... (4 Replies)
Discussion started by: muzaffar.k
4 Replies
LEARN ABOUT CENTOS
makedeltarpm
MAKEDELTARPM(8) System Manager's Manual MAKEDELTARPM(8)NAME
makedeltarpm - create a deltarpm from two rpms
SYNOPSIS
makedeltarpm [-v] [-V version] [-z compression] [-m mbytes] [-s seqfile] [-r] [-u] oldrpm newrpm deltarpm
makedeltarpm [-v] [-V version] [-z compression] [-s seqfile] [-u] -p oldrpmprint oldpatchrpm oldrpm newrpm deltarpm
DESCRIPTION
makedeltarpm creates a deltarpm from two rpms. The deltarpm can later be used to recreate the new rpm from either filesystem data or the
old rpm. Use the -v option to make makedeltarpm more verbose about its work (use it twice to make it even more verbose).
If you want to create a smaller and faster to combine "rpm-only" deltarpm which does not work with filesystem data, specify the -r option.
makedeltarpm normally produces a V3 format deltarpm, use the -V option to specify a different version if desired. The -z option can be used
to specify a different compression method, the default is to use the same compression method as used in the new rpm.
The -s option makes makedeltarpm write out the sequence id to the specified file seqfile.
If you also use patch rpms you should use the -p option to specify the rpm-print of oldrpm and the created patch rpm. This option tells
makedeltarpm to exclude the files that were not included in the patch rpm but are not byteswise identical to the ones in oldrpm.
makedeltarpm can also create an "identity" deltarpm by adding the -u switch. In this case only one rpm has to be specified. An identity
deltarpm can be useful to just replace the signature header of a rpm or to reconstruct a rpm from the filesystem.
MEMORY CONSIDERATIONS
makedeltarpm normally needs about three to four times the size of the rpm's uncompressed payload. You can use the -m option to enable a
sliding block algorithm that needs mbytes megabytes of memory. This trades memory usage with the size of the created deltarpm. Furthermore,
the uncompressed deltarpm payload is currently also stored in memory when this option is used, but it tends to be small in most cases.
SEE ALSO applydeltarpm(8)combinedeltarpm(8)AUTHOR
Michael Schroeder <mls@suse.de>
Jul 2010 MAKEDELTARPM(8)
06-28-2012
