From: Jeff Sturm <jsturm@one-point.com>
To: DJ Delorie <dj@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: mingw32 target broken [cygwin as well] [the saga continues]
Date: Mon, 10 Dec 2001 21:06:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.10112102342040.7123-100000@mars.deadcafe.org> (raw)
In-Reply-To: <200112102030.fBAKUEU24547@greed.delorie.com>
On Mon, 10 Dec 2001, DJ Delorie wrote:
> Newlib is an operating system, just like solaris or IRIX. It doesn't
> have to be GNU software for us to support it, it just has to support
> and allow GNU software.
Yeah. It's just that assuming a non-GNU runtime doesn't seem to fit the
ideology. (Not that GNU has anything better for embedded use... at least
newlib is free software.)
> And you can't always do a test link with
> cross compilers, because you may not have built enough support stuff
> (crt0, libc, gas/ld) to do so.
But it helps if you do. When I build a cross compiler, I typically follow
these steps:
1) Install target runtime headers.
2) Build/install cross binutils.
3) Build/install C cross compiler.
4) Build/install target runtime libraries.
5) Build/install other languages (c++, java).
At step 5) I have everything I need for AC_TRY_LINK. I could
save a lot of time if configure would first attempt to link, falling back
on the newlib guesses.
> > In the target subdirs, "target" becomes "host".
>
> Yeah, that confuses people, but it does make sense. "host" is what
> you're building *for*. For target libraries, you're building for the
> --target, so $host is --target.
That's how I understood it. But I looked in libstdc++-v3 and libjava...
the former has a configure.target script, the latter configure.host. So
that interpretation isn't uniform throughout GCC.
Jeff
next prev parent reply other threads:[~2001-12-11 5:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 21:06 mingw32 target broken Adam Megacz
2001-12-07 22:01 ` Adam Megacz
[not found] ` <20011208003722.A14955@mediaone.net>
2001-12-07 23:12 ` mingw32 target broken [cygwin as well] Adam Megacz
2001-12-07 23:40 ` Craig Rodrigues
2001-12-08 0:00 ` mingw32 target broken [cygwin as well] [didn't know cross-compilers were such an ordeal] Adam Megacz
2001-12-08 16:00 ` Jeff Sturm
2001-12-08 16:05 ` Adam Megacz
2001-12-08 14:42 ` mingw32 target broken [cygwin as well] Jeff Sturm
2001-12-08 16:04 ` mingw32 target broken [cygwin as well] [the saga continues] Adam Megacz
2001-12-08 18:19 ` Craig Rodrigues
2001-12-08 18:30 ` Adam Megacz
2001-12-08 18:39 ` Craig Rodrigues
2001-12-08 18:56 ` Adam Megacz
2001-12-09 9:07 ` Jeff Sturm
2001-12-09 20:38 ` Adam Megacz
2001-12-10 12:36 ` DJ Delorie
2001-12-10 12:48 ` Joseph S. Myers
2001-12-10 12:57 ` DJ Delorie
2001-12-10 21:06 ` Jeff Sturm [this message]
2001-12-10 21:08 ` DJ Delorie
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=Pine.LNX.4.10.10112102342040.7123-100000@mars.deadcafe.org \
--to=jsturm@one-point.com \
--cc=dj@redhat.com \
--cc=gcc@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).