From: Michael Elizabeth Chastain <mec@shout.net>
To: msarasa@fh-konstanz.de
Cc: ac131313@redhat.com, drow@mvista.com, gdb@sources.redhat.com
Subject: Re: error building gcc , (simulators and targets...)
Date: Thu, 16 Jan 2003 17:02:00 -0000 [thread overview]
Message-ID: <200301161700.h0GH0ES15211@duracef.shout.net> (raw)
That cross-gcc FAQ is dated 1999-12-03! It's the latest cross-gcc FAQ
that I've ever found. I don't think anyone is actively maintaining it.
Michael C
next reply other threads:[~2003-01-16 17:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 17:02 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-15 17:13 Michael Elizabeth Chastain
2003-01-16 9:58 ` msarasa
2003-01-16 12:54 ` msarasa
2003-01-16 13:50 ` Daniel Jacobowitz
2003-01-16 14:18 ` msarasa
2003-01-16 14:31 ` Daniel Jacobowitz
2003-01-16 15:20 ` msarasa
2003-01-15 16:50 Michael Elizabeth Chastain
2003-01-15 16:59 ` Andrew Cagney
2003-01-15 17:11 ` msarasa
2003-01-15 16:50 Daniel Jacobowitz
2003-01-15 16:48 Michael Elizabeth Chastain
2003-01-15 10:13 msarasa
2003-01-15 13:21 ` Daniel Jacobowitz
2003-01-15 16:13 ` Andrew Cagney
2003-01-15 16:15 ` Daniel Jacobowitz
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=200301161700.h0GH0ES15211@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=msarasa@fh-konstanz.de \
/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