QUESTION:
We have received some C code from a third party that drives a
plotter. When we compile it, we get unresolved references:
__quoss
__divss
According to INFO, these are part of the assembler language
"milicode", but we can't get them resolved. Is there a
library that we are missing?
---------- ---------- ---------- --------- ---------- ----------
A: We wrote a small assembler program that uses a milicode routine
(mulh), and we tried compiling it all kinds of ways. The only
way we could get it to resolve the milicode routine was to set
the LIBPATH environment variable to /usr/lib/FCM:/usr/lib:/lib
and then compile the file with the following command:
cc -c asm.s -qarch=COM -qdebug=useabs -bI:/usr/lib/FCM/lowsys.exp
where asm.s is the assembler source file that calls the milicode
routine. Actually, the -qarch and -qdebug options are optional,
but the information we found in our local database recommends that
they be used. The above compile command generates an asm.o object
file that can then be linked to the executable.
Of course, to resolve these symbols, you will have to have a
/usr/lib/FCM directory with a libc.a and a lowsys.exp file in it.
The libc.a in this directory contains the milicode routines. If
you do not have the /usr/lib/FCM directory you can get it with
PTF's U432415 and U432416. AIX 3.2.5 is a prerequisite.
---------- ---------- ---------- --------- ---------- ----------
This item was created from library item Q676834 FFMDB
Additional search words:
ASSEMBLER COMPILERS EXTERN EXTERNAL FFMDB IX JAN95 LANGUAGE MILICODE
OZIBM OZNEW PROGRAM REFERENCE REFERENCES RISCL RISCSYSTEM ROUTINES
SOFTWARE UNRESOLVED URGENT
WWQA: ITEM: RTA000053126 ITEM: RTA000053126
Dated: 06/1996 Category: RISCL
This HTML file was generated 99/06/24~12:43:21
Comments or suggestions?
Contact us