Sponsored Content
Full Discussion: shared lib issue
Operating Systems HP-UX shared lib issue Post 302151466 by porter on Saturday 15th of December 2007 03:59:36 PM
Old 12-15-2007
That looks like a problem with dynamic loading.

1.Have you built all shared libraries?

2. Are any of the shared libraries implemented in C++?

3. Did you use the same compiler on *all* modules, shared and application?

4. Have you tried "ldd"? Can this resolve all modules?

5. Please post "uname -a" of system. Is this 32 bit/64 bit, PA-RISC or Itanium?

Another feature of HPUX is that unless you are careful the build process won't warn you of unresolved dependencies.

Last edited by porter; 12-15-2007 at 05:13 PM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

What happens when an exe/lib links to another shared one:

We build our code on all platforms Sol, Hp, Aix, Sgi & linux. Some base libraries have changed. All the dependent exe & lib which use those base libraries have changed in all platforms in terms of size/checksum or both except linux. No code has changed in these. We have a post utility... (8 Replies)
Discussion started by: vibhor_agarwali
8 Replies

2. UNIX for Advanced & Expert Users

Issue with shared object in AIX

Hi All, I have a problem with the shared objects setup in AIX. We have a customized shell written by the developers over here. When i issue a MQ Series command (mqsilist) it is giving the error as . All the commands making use of this libImbCmdLib.a.so is failing. But when executed in normal... (1 Reply)
Discussion started by: dhanamurthy
1 Replies

3. AIX

Shared memory issue

Hi friends.. Help to solve this issue... Is there any parameter setting to control or limit the size of the shared memory a process can attach for the below specified environment? The man pages says it can attach upto segments of size 2GB. But when our process (which also connects to... (0 Replies)
Discussion started by: sdspawankumar
0 Replies

4. HP-UX

Shared Library Issue HP UX

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)
Discussion started by: sambarusty
3 Replies

5. Red Hat

ls: /lib/libattr.so.1: no version information available (required by /lib/libacl.so.1)

Hello, I'm experimenting a problem on my rh server. Red Hat Enterprise Linux AS release 3 (Taroon Update 8) 2.4.21-47.ELsmp #1 SMP i686 i686 i386 GNU/Linux It started with a segmentation fault on #id root To resolve it, I've installed coreutils-4.5.3-28.4.i386.rpm But, I... (6 Replies)
Discussion started by: gogol_bordello
6 Replies

6. Programming

Can I create a shared object by using an static lib?

for example, I have a static lib name liba.a it offers some interface such a1();a2(); but i do not have the source code of liba.a; If i would like to create a shared object, and offer the similar interface of a1 and a2; Is there a way to fulfill such requirement? thanks. (7 Replies)
Discussion started by: flost
7 Replies

7. AIX

AIX 5.2 C++ shared object issue

Hi all, I am developing an application with two components. One "c" binary and one "C++" shared object. While execution, the shared object crashes out and core dump is created whenever "new" is executed. But if i use malloc this will work perfectly. I tried to use dbx. Below given was... (1 Reply)
Discussion started by: itssujith
1 Replies

8. Linux

Permission denied issue on a Shared drive

Hi, I have 2 linux servers. One of them has a mount which I have mapped to a shared samba directory on the other server. Below will help you understand better. smb.conf on Server1: workgroup = WRKGRP netbios name = smbserver security = SHARE load printers = No default service = global... (11 Replies)
Discussion started by: satishrao
11 Replies

9. Shell Programming and Scripting

Shared File system- lib access issue

I have a C++ binary executable installed in a file system which is shared across multiple solaris boxes. When I start this executable from one of the boxes,I am able to start only 4 parallel instances and from the 5th instance onwards I am getting the following error. fatal: libdb2.so.1:... (2 Replies)
Discussion started by: prasperl
2 Replies

10. Programming

Shared library with acces to shared memory.

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
fastbind(1)						      General Commands Manual						       fastbind(1)

NAME
fastbind - Prepare an incomplete executable for faster program start-up SYNOPSIS
incomplete-executable... DESCRIPTION
is a tool that can improve the start-up time of programs that use shared libraries (incomplete executables) by storing information about needed shared library symbols in the executable file. performs analysis on the symbols used to bind an executable and all of it's dependent shared libraries, and stores this information in the executable file. The next time the executable is run, the dynamic loader will notice that this information is available, and it will use this fastbind information to bind the executable instead of the standard search method for binding the symbols. For Itanium-based systems, the dynamic loader is for 32-bit mode or for 64-bit mode. For PA-RISC systems, the dynamic loader is for 32-bit mode or for 64-bit mode. Since writes the fastbind information in the executable file, you must have write permission on the executable file. Also, if the exe- cutable file being analyzed is being run as another process, the file will be locked against modifications by the kernel, and will fail. If the shared libraries that an executable is dependent on are modified after the fastbind information is created, the dynamic loader will silently revert to standard search method for binding the symbols. The fastbind information can be re-created by running on the executable again. will automatically erase the old fastbind information and generate the new one. The option can be used to instruct the linker to run the fastbind tool on an incomplete executable it has produced. Environment Variables If determines that the fastbind information is out of date, it will silently revert to standard search method for binding the symbols. If the environment variable is set to the dynamic loader will emit a warning message when the fastbind information is out of date. The environment variable can be set to to make the dynamic loader ignore the fastbind information and revert to the standard search method for binding the symbols. Options recognizes the following options: Remove the fastbind information from the executable, returning it to the same state it was in before was originally run on it. Normally, if detects any unsatisfied symbols while building the fastbind information, it will generate an error message and not mod- ify the executable file. When is invoked with option however, unresolved symbols are allowed. EXTERNAL INFLUENCES
Environment Variables The following internationalization variables affect the execution of Determines the locale category for native language, local customs and coded character set in the absence of and other environment variables. If is not specified or is set to the empty string, a default of (see lang(5)) is used instead of Determines the values for all locale categories and has precedence over and other environment variables. Determines the locale that should be used to affect the format and contents of diagnostic messages written to standard error. Determines the locale category for numeric formatting. Determines the locale category for character handling functions. Determines the location of message catalogs for the processing of If any internationalization variable contains an invalid setting, behaves as if all internationalization variables are set to See envi- ron(5). In addition, the following environment variable affects Specifies a directory for temporary files (see tmpnam(3S)). DIAGNOSTICS
returns zero when the operation is successful. A non-zero return code indicates that an error occurred. EXAMPLES
To run on the executable file enter: To later remove the fastbind information from the executable file enter: WARNINGS
32-bit PA-RISC does not work with EXEC_MAGIC executables. effectively enforces bind restricted and bind immediate. For example, consider an executable linked bind deferred, which calls a function foo() defined in an implicitly loaded library. Before the actual call is made, if it explicitly loads a shared library (using shl_load(3X) with having a definition for when is finally called, it will be resolved from the explicitly loaded library. But after running the symbol will be resolved from the implicitly loaded library. AUTHOR
was developed by Hewlett-Packard. FILES
output file 32-bit PA-RISC dynamic loader 32-bit Itanium-based dynamic loader 64-bit PA-RISC dynamic loader 64-bit Itanium-based dynamic loader message catalog temporary files SEE ALSO
System Tools ld(1) invoke the link editor Miscellaneous a.out(4) assembler, compiler, and linker output dld.sl(5) PA-RISC dynamic loader dld.so(5) Itanium-based dynamic loader Texts and Tutorials
All times are GMT -4. The time now is 04:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy