1752630
Members
6053
Online
108788
Solutions
SOLVED
/usr/ccs/bin/ld: /opt/OV/lib: Not a valid object file (invalid system id)
this is because the link line had /opt/OV/lib as an input file to ld. it should have followed a '-L'. this has nothing to do with 32/64 bit. header file problems cannot be solved by changing from 32-bit to 64-bit.
as for unresolved symbols, i think compiling and linking with aCC (instead of gcc) may resolve the problem.
--
ranga
[i work for hpe]
this is because the link line had /opt/OV/lib as an input file to ld. it should have followed a '-L'. this has nothing to do with 32/64 bit. header file problems cannot be solved by changing from 32-bit to 64-bit.
as for unresolved symbols, i think compiling and linking with aCC (instead of gcc) may resolve the problem.
--
ranga
[i work for hpe]
here is the reason why the unresolved symbols appear: libraries libstd.2, libov.3 and libsnmp.3 are built with aCC. so they have references to symbols defined in libCsup.sl.
now you did not compile/link with aCC so your program does not link with libCsup.sl. hence the unresolved symbols.
there are a few ways to resolve this:
1. build your application with aCC so that libCsup is included in the link line by the compiler. all other related problems are also avoided.
2. link your application with libCsup by adding the following to CFLAGS: -lCsup
3. use LD_PRELOAD to preload libCsup at run-time. you can do this with the command
LD_PRELOAD=/usr/lib/libCsup.sl ./AlcPabxPolling
compiling and linking for PA64 instead of PA32 may solve your problem in some mysterious way but you may not be able to do it all the time.
--
ranga
[i work for hpe]
now you did not compile/link with aCC so your program does not link with libCsup.sl. hence the unresolved symbols.
there are a few ways to resolve this:
1. build your application with aCC so that libCsup is included in the link line by the compiler. all other related problems are also avoided.
2. link your application with libCsup by adding the following to CFLAGS: -lCsup
3. use LD_PRELOAD to preload libCsup at run-time. you can do this with the command
LD_PRELOAD=/usr/lib/libCsup.sl ./AlcPabxPolling
compiling and linking for PA64 instead of PA32 may solve your problem in some mysterious way but you may not be able to do it all the time.
--
ranga
[i work for hpe]
to make it simple - because of the unresolved symbols problem i recommend that you use aCC.
if you prefer gcc, perhaps you should try compiling it with the correct version as others have suggested. if the problem of unresolved symbols is still not solved, i think using aCC is the solution.
--
ranga
[i work for hpe]
if you prefer gcc, perhaps you should try compiling it with the correct version as others have suggested. if the problem of unresolved symbols is still not solved, i think using aCC is the solution.
--
ranga
[i work for hpe]
try aCC if you have it.
--
ranga
[i work for hpe]
--
ranga
[i work for hpe]