From: "Russ.Shaw" <russell@webaxs.net>
To: egcs@cygnus.com
Cc: crossgcc@sourceware.cygnus.com
Subject: Library and linker errors
Date: Tue, 01 Aug 2000 22:49:00 -0000 [thread overview]
Message-ID: <3987B6DA.61538FBF@webaxs.net> (raw)
In-Reply-To: <001101c01fe1$7e10b260$58210b0a@huawei.com.cn>
Hi all,
I'm using gcc-2.95.5 configured as a cross-compiler for the
hitachi H8/300H cpu core. I'm using mandrake-7.0.
I found that h8300-hms-gcc gets its library files from:
/usr/local/h8300-hms/lib/libc.a
libg.a
libm.a
libiberty.a
and
/usr/local/lib/h8300-hms/libgcc.a (iirc)
However, i get lots of linker errors like:
/usr/local/h8300-hms/lib/libg.a(strtol.o)(.text+0xfa):strtol.c:
undefined reference to '__umodsi3'
/usr/local/h8300-hms/lib/libg.a(strtol.o)(.text+0x10a):strtol.c:
undefined reference to '__udivsi3'
/usr/local/h8300-hms/lib/libg.a(strtol.o)(.text+0x152):strtol.c:
undefined reference to '__umulsi3'
I can't find where __umodsi3 etc are defined. In my makefile, i'm
linking ld using -lgcc -liberty -lg -lc -lm.
--
*******************************************
* Russell Shaw, B.Eng, M.Eng(Research) *
* email: russell@webaxs.net *
* Australia *
*******************************************
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-08-01 22:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-26 6:28 error in building arm-elf gcc Jun Wu
2000-07-26 18:24 ` Joel Sherrill
2000-07-31 21:30 ` How to link in <string.h> object file? Russ.Shaw
2000-08-01 11:19 ` error in building arm-elf gcc Joel Sherrill
2000-08-01 22:49 ` Russ.Shaw [this message]
2000-08-01 23:10 ` Library and linker errors Doug Evans
2000-08-02 2:27 ` Russ.Shaw
2000-08-02 9:57 ` Doug Evans
2000-08-02 4:32 ` gcc, crt0, and linker scripts Russ.Shaw
2000-08-02 6:08 ` Russ.Shaw
2000-08-02 10:04 ` Doug Evans
2000-08-02 16:51 ` Russ.Shaw
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=3987B6DA.61538FBF@webaxs.net \
--to=russell@webaxs.net \
--cc=crossgcc@sourceware.cygnus.com \
--cc=egcs@cygnus.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).