HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- dld.sl: Bad magic number for shared
Operating System - HP-UX
1830477
Members
2434
Online
110005
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
Forums
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
10-06-2001 07:48 AM
10-06-2001 07:48 AM
dld.sl: Bad magic number for shared
on hp-ux 11.0, whenever i call libexport.dl client from an application, rather it loads it, gives the followin alarm
Alarm message: Cannot initialize API CLIENT
and gives the same following warning on console
/usr/lib/dld.sl: Bad magic number for shared library: /home/manju/FiltersDepot/smexport/Source/OBJPIC/libexport.dl
/usr/lib/dld.sl: Exec format error
Alarm message: Cannot initialize API CLIENT
and gives the same following warning on console
/usr/lib/dld.sl: Bad magic number for shared library: /home/manju/FiltersDepot/smexport/Source/OBJPIC/libexport.dl
/usr/lib/dld.sl: Exec format error
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2001 09:54 AM
10-06-2001 09:54 AM
Re: dld.sl: Bad magic number for shared
What do you get if you do a file on the shared library, i.e.:
file /home/manju/FiltersDepot/smexport/Source/OBJPIC/libexport.dl
you should get something like :
PA-RISC1.1 shared library -not stripped
otherwise either there is something wrong with the library or it was build for a different platform, e.g. Sun Sparc or Linux.
-Santosh
file /home/manju/FiltersDepot/smexport/Source/OBJPIC/libexport.dl
you should get something like :
PA-RISC1.1 shared library -not stripped
otherwise either there is something wrong with the library or it was build for a different platform, e.g. Sun Sparc or Linux.
-Santosh
Life is what's happening while you're busy making other plans
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-07-2001 11:12 AM
10-07-2001 11:12 AM
Re: dld.sl: Bad magic number for shared
Hi Sunil,
Not sure if this will help you or not,
From the HP Doc KBRC00000398
"bad magic number" and "exec" errors from dld.sl
/Begin/
Possible causes and the fixes are:
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.
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.
If /lib is not linked to /usr/lib, then the shared libraries will not have a reference point.
ln -s /usr/lib /lib
/End/
-HTH
Ramesh
Not sure if this will help you or not,
From the HP Doc KBRC00000398
"bad magic number" and "exec" errors from dld.sl
/Begin/
Possible causes and the fixes are:
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.
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.
If /lib is not linked to /usr/lib, then the shared libraries will not have a reference point.
ln -s /usr/lib /lib
/End/
-HTH
Ramesh
They think they know but don't. At least I know I don't know - Socrates
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP