From: swamp-dog@ntlworld.com (Guy Harrison)
To: <cygwin@cygwin.com>
Subject: Re: Problems linking program
Date: Sun, 21 Apr 2002 13:46:00 -0000 [thread overview]
Message-ID: <3cc411d5.271181939@smtp.ntlworld.com> (raw)
In-Reply-To: <5.1.0.14.2.20020419152307.02585d38@mail.prefres.com>
On Fri, 19 Apr 2002 15:25:27 -0500, "Matt Minnis" <mminnis@prefres.com>
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]
--
swamp-dog@ntlworld.com
--
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/
next prev parent reply other threads:[~2002-04-21 20:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 11:18 Matt Minnis
2002-04-18 12:37 ` Larry Hall (RFK Partners, Inc)
2002-04-19 13:42 ` Matt Minnis
2002-04-21 13:46 ` Guy Harrison [this message]
2002-04-21 19:49 ` Larry Hall (RFK Partners, Inc)
2002-04-22 11:40 Matt Minnis
2002-04-22 12:11 ` Larry Hall (RFK Partners, Inc)
2002-04-22 12:55 ` Charles Wilson
2002-04-22 13:25 ` Larry Hall (RFK Partners, Inc)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3cc411d5.271181939@smtp.ntlworld.com \
--to=swamp-dog@ntlworld.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).