From: "Russ.Shaw" <russell@webaxs.net>
To: crossgcc@sourceware.cygnus.com
Subject: Re: How to link in <string.h> object file?
Date: Mon, 31 Jul 2000 23:40:00 -0000 [thread overview]
Message-ID: <39867115.A736A6CB@webaxs.net> (raw)
In-Reply-To: <14726.25455.163000.360698@nokia.com>
Hi all,
I figured that the files in:
/usr/local/h8300-hms/lib are what i need to link:
libc.a
libg.a
libm.a
libgcc.a
libiberty.a
Is there stated somewhere what functions are contained in
what libraries? What does libiberty.a contain?
Also, when i linked in one of these libraries in my makefile,
i got lots of errors referring to linker script sections,
probably because i'm using my own script without ctor or
dtor etc. I assume one is supposed to use one of these:
/usr/local/h8300-hms/lib/ldscripts/h8300h.x
h8300h.xbn
h8300h.xn
h8300h.xr
h8300h.xu
I'm using my own system with eproms etc, so would it be
ok to just use a modified one of these scripts to fix
the errors?
Darin Johnson wrote:
>
> You need the Gnu C library, which may not be included with
> the compiler. It's in the "glibc" directory at GNU ftp sites.
> (check out the readme files, as newer version may no support
> as many types of machines as they used to)
--
*******************************************
* 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 parent reply other threads:[~2000-07-31 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <398652CC.49D08980@webaxs.net>
[not found] ` <14726.25455.163000.360698@nokia.com>
2000-07-31 23:40 ` Russ.Shaw [this message]
2000-08-01 6:43 ` Matthew Majka
2000-07-26 6:28 error in building arm-elf gcc Jun Wu
2000-07-31 21:30 ` How to link in <string.h> object file? 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=39867115.A736A6CB@webaxs.net \
--to=russell@webaxs.net \
--cc=crossgcc@sourceware.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).