Operating System - Linux
1828667 Members
1661 Online
109984 Solutions
New Discussion

Bad system id for shared library

 
SOLVED
Go to solution
d'arco
Frequent Advisor

Bad system id for shared library

Hi Procura,

with your help I installed libpng depot under UX 10.20.

I could finish the installation of the product which you do not like.

When I start it (xemacs) I have the following error :
"
/usr/lib/dld.sl: Bad system id for shared library: /opt/libpng/lib/libpng.sl
/usr/lib/dld.sl: Exec format error
"

The model of my workstation is : 9000/779/C160L

Do I need to recompile something ?
15 REPLIES 15
Arunvijai_4
Honored Contributor

Re: Bad system id for shared library

Run file command on /opt/libpng/lib/libpng.sl and let us know the result.

-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
d'arco
Frequent Advisor

Re: Bad system id for shared library

Hi,

I can not execute /opt/libpng/lib/libpng.sl
when do it, I have the following error :
"sh: /opt/libpng/lib/libpng.sl: Execute permission denied."

the properties are :
lrwxrwxr-x 1 root sys 11 Sep 20 23:12 libpng.sl -> libpng.sl.3
lrwxr-xr-x 1 root sys 17 Sep 20 19:30 libpng.sl.3 -> libpng.sl.3.1.2.7
-rwxr-xr-x 1 root sys 242331 Oct 4 2004 libpng.sl.3.1.2.7

I am root. I don't know how to execute libpng.sl ???
Arunvijai_4
Honored Contributor

Re: Bad system id for shared library

You can't execute a shared library. It is library file (/opt/libpng/lib/libpng.sl). Dynamically linked executables will pick shared libararies automatically if they are in library path.

-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
Muthukumar_5
Honored Contributor
Solution

Re: Bad system id for shared library

Export SHLIB_PATH to /opt/libpng/lib location and try to start it.

hth.
Easy to suggest when don't know about the problem!
d'arco
Frequent Advisor

Re: Bad system id for shared library

I set $SHLIB_PATH to /opt/libpng/lib and when I start xemacs, I have the following error :

"/usr/lib/dld.sl: Invalid shared library file: /opt/libpng/lib/libpng.sl
Abort(coredump)"

I am not sure that it is this information which you want?
Arunvijai_4
Honored Contributor

Re: Bad system id for shared library

Send us output of

# file
# file /opt/libpng/lib/libpng.sl
# chatr /opt/libpng/lib/libpng.sl

-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
VEL_1
Valued Contributor

Re: Bad system id for shared library

Hi,

It may 32 & 64 bit problem. Just find it 32 bit libpng.sl or 64 bit libpng.sl?

# file /opt/libpng/lib/libpng.sl

you may need 32 bit /opt/libpng/lib/libpng.sl.

Thanks.
d'arco
Frequent Advisor

Re: Bad system id for shared library

Hi,

hereafter the response of the commands :

[arachne]:root > file libpng.sl
libpng.sl: PA-RISC2.0 shared library -not stripped
[arachne]:root > chatr libpng.sl
libpng.sl:
shared library
shared library dynamic path search:
SHLIB_PATH disabled first
embedded path disabled second Not Defined
internal name:
libpng.sl.3
shared vtable support disabled
static branch prediction disabled
kernel assisted branch prediction enabled
lazy swap allocation disabled
text segment locking disabled
data segment locking disabled
data page size: 4K
instruction page size: 4K

[arachne]:root > file xemacs
xemacs: PA-RISC1.1 shared executable dynamically linked


I have no path for xemacs.
Stephen Keane
Honored Contributor

Re: Bad system id for shared library

Where did you get libpng.sl from? It looks like a 64-bit version.
d'arco
Frequent Advisor

Re: Bad system id for shared library

Hi,

Procura give me the depot for libpng.

I don't konw if it is a 32 or 64-bit !!
Arunvijai_4
Honored Contributor

Re: Bad system id for shared library

I am not sure your /opt/libpng/lib/libpng.sl is a 64 bit library. It is 32 bit but, it is for PA2.0 shared library. I think, it wont work on your 10.20 since it will support only PA-RISC1.1 libraries, Xemacs executable is PA-RISC1.1. Ask procura to provide PA-RISC1.1 compatible library. (+DA1.1 will do while compiling)

-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
Muthukumar_5
Honored Contributor

Re: Bad system id for shared library

ibpng.sl: PA-RISC2.0 shared library -not stripped It is not related with xemacs: PA-RISC1.1 shared executable dynamically linked.

I hope you are using wrong libpng.sl library. Try to build with PA-RISC1.1 compiler option.

hth.
Easy to suggest when don't know about the problem!
d'arco
Frequent Advisor

Re: Bad system id for shared library

Hi,

Procura indicated the good shared library to be used.

Now I have a problem with Xemacs (path, configuration,.....). When I start Xemacs I have the following error :

WARNING:
Couldn't find an obvious default for the root of the
XEmacs hierarchy.
WARNING:
Couldn't find obvious defaults for:
doc-directory
data-directory
exec-directory
Perhaps some directories don't exist, or the XEmacs executable,
/usr/local/bin/xemacs
is in a strange place?Cannot open load file: /opt/bintmp/xemacs-21.1.14/lisp/auto-autoloads




Do Anyone know the problem ???
Arunvijai_4
Honored Contributor

Re: Bad system id for shared library

I think, its a known problem of Xemacs with HP-UX. Just go through this link, http://list-archive.xemacs.org/xemacs-beta/200109/msg00345.html
and read followup http://list-archive.xemacs.org/xemacs-beta/200109/msg00352.html.

It says, you need to compile again on your system.

I finally found a similar thread in ITRC,
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=579653

(Just try to create symlinks where it is needed)

-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
ranganath ramachandra
Esteemed Contributor

Re: Bad system id for shared library

you are trying to use PA2.0 versions on PA1.1 (hpux 10.20). you need the PA1.1 (hpux 10.20) versions of the depots.
 
--
ranga
hp-ux 11i v3[i work for hpe]

Accept or Kudo