On Fri, 19 Apr 2002 15:25:27 -0500, "Matt Minnis" <[EMAIL PROTECTED]>
wrote:
>Larry,
>
>I did an nm -C and collected the output to a text file.
>I found references to these functions in libc, libg, and libcygwin.
>I am not quite sure what to look for now.
>Can you explain what I need to be looking for?
In the case of functions, big 'T's ;-)
Loosely: Definitions. One thereof. Multiple definitions means you have
to make an executive decision about which lib was intended, and no
definition implies "go download missing package" or "bad config wrong
machine".
nm -A --defined-only `find /lib -name '*.a'` | grep umoddi3
[snip path]/libgcc.a:_umoddi3.o:00000000 b .bss
/libgcc.a:_umoddi3.o:00000000 d .data
/libgcc.a:_umoddi3.o:00000000 ? .stab
/libgcc.a:_umoddi3.o:00000000 ? .stabstr
/libgcc.a:_umoddi3.o:00000000 t .text
/libgcc.a:_umoddi3.o:00000000 t ___clz_tab
/libgcc.a:_umoddi3.o:00000000 t ___gnu_compiled_c
/libgcc.a:_umoddi3.o:00000100 T ___umoddi3
/libgcc.a:_umoddi3.o:00000000 t gcc2_compiled
...implies "-lgcc" is missing from the link line. Now you're certainly
on your own because that's automatically done via "specs".
[snip]
--
[EMAIL PROTECTED]
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
