- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Bad system id when loading a library
Operating System - HP-UX
1759497
Members
2924
Online
108883
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2000 01:12 PM
05-12-2000 01:12 PM
Hi,
We have an application that tries to load a library. The error we get is
/usr/lib/dld.sl: Bad system id for shared library: /software/d236test/hps_apps/bin/ZFFDVZF.dll
/usr/lib/dld.sl: Exec format error
I know it says dll but it really is a library and we do this all the time (not with this particular library). This library was sent to us from a client. I'm just curious what a bad system id means?
System: HP9000, HP-UX 11. Client has same set up as well.
Thanks,
Brian
We have an application that tries to load a library. The error we get is
/usr/lib/dld.sl: Bad system id for shared library: /software/d236test/hps_apps/bin/ZFFDVZF.dll
/usr/lib/dld.sl: Exec format error
I know it says dll but it really is a library and we do this all the time (not with this particular library). This library was sent to us from a client. I'm just curious what a bad system id means?
System: HP9000, HP-UX 11. Client has same set up as well.
Thanks,
Brian
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2000 11:07 PM
05-14-2000 11:07 PM
Solution
Possible causes and the fixes are:
1.If libc is older than dld.sl or vice versa, then the two libraries will have
difficulties understanding each other. Update both by installing the latest
libc and dld.sl patches.
2.If the error was encountered while attempting to run a COBOL program, then
it is possible that the executable was created on a PA1.1 machine using a
shared library that was created on a PA2.0 machine. The linker did not give the
typical warning that a PA2.0 object was detected. Instead, the only error
returned occurred at runtime, when dld.sl attempted to bind the shared libraries.
The only solutions are to:
compile and run the program on the same machine.
install the latest dld.sl and libc patches on both machines and recompile.
3.If /lib is not linked to /usr/lib, then the shared libraries will not have a reference
point.
ln -s /usr/lib /lib
1.If libc is older than dld.sl or vice versa, then the two libraries will have
difficulties understanding each other. Update both by installing the latest
libc and dld.sl patches.
2.If the error was encountered while attempting to run a COBOL program, then
it is possible that the executable was created on a PA1.1 machine using a
shared library that was created on a PA2.0 machine. The linker did not give the
typical warning that a PA2.0 object was detected. Instead, the only error
returned occurred at runtime, when dld.sl attempted to bind the shared libraries.
The only solutions are to:
compile and run the program on the same machine.
install the latest dld.sl and libc patches on both machines and recompile.
3.If /lib is not linked to /usr/lib, then the shared libraries will not have a reference
point.
ln -s /usr/lib /lib
There is no good troubleshooting with bad data
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP