06-22-2007 12:55 PM
Have an application - worked out the compile bugs with the nice folks here.
Now the link in with some existing c code.
I added libstream.a and libstd_v2.a and I Still get:
set_new_handler__3stdFPFv_v (first referenced in /vobs/build/devlib/libdcm.a(dcmif_api.o)) (code)
[Vtable]key:__dt__Q2_3std9exceptionFv (first referenced in /usr/lib/libstd_v2.a(char.o)) (data)
typeid__XTQ2_3std9exception_ (first referenced in /vobs/build/devlib/libdcm.a(dcmif_api.o)) (data)
__dt__Q2_3std9exceptionFv (first referenced in /vobs/build/devlib/libdcm.a(dcmif_api.o)) (code)
__nw__FUi (first referenced in /vobs/HP-UX_stage/lib/libi4nsi.a(nsiint.o)) (code)
dcmif_api.cpp is NOT the first cpp in the archive but it doesn't look "dangerous" either.
06-22-2007 01:36 PM
>I added libstream.a and libstd_v2.a
You can NOT mix -AP and -AA libs. Remove libstream.
Also, why are you using archive libs? Stick with shared libs.
06-25-2007 09:42 AM
"If you compile with -AA you must link with -AA."
ld doesn't look like it has an -AA option.
/usr/ccs/bin/ld: Can't open A
/usr/ccs/bin/ld: No such file or directory
Do I need to explitily add any libs on this transition? Like libstd_v2 ?
06-29-2007 02:36 PM
It is not legal to directly use ld to link C++ applications or shlibs.
So the statement you must link with -AA means you must use "aCC -AA" at link time.
You haven't assigned any points to the responses in this thread. Is there some answers you still need?
Please read this.
You can reopen the thread: