4 replies to this topic

[Jason Tee]

I wonder any experts can solve this for me. During installing Proiv 46r523 Solaris 64 bits and Oracle version is 9.2.0.1 64 bits but got this error as below :-


Build: Dialogue; Started at Wed May 26 11:47:45 2004.
Build: Dialogue; The PRO-IV serialization file has now been updated.
Build: Dialogue; Please wait ... PRO-IV is now being configured.
Build: Dialogue; Linking PRO-IV with Oracle v9i (9.x.x)
Build: Dialogue; Linking the PRO-IV kernel ...
ld: fatal: file /usr/lib/libnsl.so: wrong ELF class: ELFCLASS32
ld: fatal: file /usr/lib/libsocket.so: wrong ELF class: ELFCLASS32
ld: fatal: file /usr/ccs/lib/libgen.so: wrong ELF class: ELFCLASS32
ld: fatal: file /usr/lib/libdl.so: wrong ELF class: ELFCLASS32
ld: fatal: file /usr/ucblib/libucb.so: wrong ELF class: ELFCLASS32
ld: fatal: File processing errors. No output written to /pro4/pro46r523/bin/pro
Build: Warning; The build process failed whilst linking the PRO-IV kernel.
Build: Warning; Please examine the script file (/pro4/pro46r523/bs/kernlink) to locate the problem.
Build: Warning; Re-invoke the script using the command "/pro4/pro46r523/bs/./kernlink" to complete.
Build: Warning; Configuration procedure has failed.

[Cleve Haynes]

Hi

I had this myself when I installed ProIV 64 bit on Solaris.

The problem is that you are trying to link 32 bit libraries against 64 bit code. You cannot do this.

You need to set your LD_LIBRARY_PATH to point to the 64 bit shared libraries, as Solaris contains both 32 & 64 bit shared libraries.

The 64 bit libraries normally live in a subdirectory called "sparcv9".

So you probably only need to do something like this (assuming bourne shell):

LD_LIBRARY_PATH=/usr/lib/sparcv9:/lib/sparcv9:/usr/local/lib/sparcv9:/usr/cc
s/lib/sparcv9:/usr/ucblib/sparcv9
export LD_LIBRARY_PATH

If you still have some files not being found, do a search for those shared libraries and then add the path of the 64 bit libraries to LD_LIBRARY_PATH.
eg:

find / -name libnsl.so -print

HTH's

Cleve

[Jason Tee]

Hi Cleve,

Somehow I have solved it with different Telnet program. Still don understand ??????

Thanks.

[Cleve Haynes]

Hi

Perhaps the shell you logged in with on your second try set the LD_LIBRARY_PATH correctly.

When you login as the root user, do you log straight in through telnet or do you log in as yourself and then use the "su -" command? Different ways of logging in and different default shells can affect which startup scripts are run. (Like .profile, .login, .cshrc etc).

Cleve

[Jason Tee]

Hi Cleve,

I used root straight away.