From: Rick Mann <rmann@latencyzero.com>
To: gcc-help@gcc.gnu.org
Subject: Modifying the std C libraries
Date: Mon, 17 Mar 2008 22:50:00 -0000 [thread overview]
Message-ID: <571CD048-5DA5-4978-B68D-1136AA528759@latencyzero.com> (raw)
We've got an xscale-elf cross compiler built using binutils, gcc 4,
and newlib. It all seems to work reasonably well. Now we've reached a
point where we must strip out all uncalled source code from newlib,
and rebuild that.
I tried the experiment of building a new newlib with the xscale-elf
tools, which worked fine, and then making a simple test program that
linked against printf(), then removing printf() and rebuilding newlib
and relinking. I would expect it to fail, but it doesn't.
I wonder if GCC is implicitly linking against the newlib that was
built with it, rather than my new newlib (even though i specify -I and
-L and -lc).
How can I get GCC to ignore the stuff it would normally implicitly
link against and instead link against a very specific version of the
runtime libs?
TIA,
--
Rick
next reply other threads:[~2008-03-17 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 22:50 Rick Mann [this message]
2008-03-17 22:58 ` Brian Dessent
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=571CD048-5DA5-4978-B68D-1136AA528759@latencyzero.com \
--to=rmann@latencyzero.com \
--cc=gcc-help@gcc.gnu.org \
/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).