From: James E Wilson <wilson@specifix.com>
To: Greg Schafer <gschafer@zip.com.au>
Cc: David Daney <ddaney@avtrex.com>,
gcc@gcc.gnu.org, binutils@sources.redhat.com
Subject: Re: RFH: libgcc_s.so being unnecessarily linked for mipsel-linux cross compiler...
Date: Fri, 29 Jul 2005 00:22:00 -0000 [thread overview]
Message-ID: <1122596557.23426.41.camel@aretha.corp.specifix.com> (raw)
In-Reply-To: <20050728235800.GA5100@tigers-lfs.nsw.bigpond.net.au>
On Thu, 2005-07-28 at 16:58, Greg Schafer wrote:
> Glibc headers ARE provided -> inhibit_libc NOT defined -> optimal
> Glibc headers ARE NOT provided -> inhibit_libc IS defined -> suboptimal
This is basically what I meant, but I don't want to get in a debate
about what is optimal and what isn't. Maybe I should have used a
different word.
Anyways, I regard Dan Kegel's crosstools as the best source of info on
doing linux cross toolchain builds. His scripts get this right, and
aren't very hard to use. There are also other ways of getting the same
result.
--
Jim Wilson, GNU Tools Support, http://www.specifix.com
next prev parent reply other threads:[~2005-07-29 0:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 19:48 David Daney
2005-07-28 20:37 ` H. J. Lu
2005-07-28 20:54 ` David Daney
2005-07-29 0:31 ` H. J. Lu
2005-07-29 0:44 ` David Daney
2005-07-28 21:26 ` James E Wilson
2005-07-28 21:47 ` Richard Henderson
2005-07-28 23:58 ` Greg Schafer
2005-07-29 0:22 ` James E Wilson [this message]
2005-07-29 0:35 ` Mike Frysinger
2005-07-29 5:11 ` Richard Sandiford
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=1122596557.23426.41.camel@aretha.corp.specifix.com \
--to=wilson@specifix.com \
--cc=binutils@sources.redhat.com \
--cc=ddaney@avtrex.com \
--cc=gcc@gcc.gnu.org \
--cc=gschafer@zip.com.au \
/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).