From: Philip Blundell <philb@gnu.org>
To: "David Feustel" <dfeustel@mindspring.com>
Cc: "David Korn" <dkorn@pixelpower.com>, crossgcc@sources.redhat.com
Subject: Re: gcc compile
Date: Sun, 01 Apr 2001 00:00:00 -0000 [thread overview]
Message-ID: <E14KGiw-00062j-00@kings-cross.london.uk.eu.org> (raw)
Message-ID: <20010401000000.YOpnq1PdDcYLJALnGFqPlmutVfDnY888VuIGFS0rSrM@z> (raw)
In-Reply-To: <01ea01c0833b$98d9bed0$6701a8c0@dafcoix6jzgi66>
>I can't find any 'sim' directory under gcc.
>Is 'sim' somewhere else in the tree?
It's bundled with GDB, not GCC. I imagine it's included in the gdb-5.0
tarball.
p.
------
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 prev parent reply other threads:[~2001-04-01 0:00 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-19 2:29 David Korn
2001-01-20 9:51 ` Philip Blundell
2001-01-20 17:15 ` David Feustel
2001-01-21 1:51 ` Philip Blundell [this message]
2001-04-01 0:00 ` Philip Blundell
2001-04-01 0:00 ` David Feustel
2001-01-20 22:49 ` Crossgcc Tutorial Docs David Feustel
2001-04-01 0:00 ` David Feustel
2001-01-22 2:53 ` gcc compile Jens-Christian Lache
2001-01-22 3:08 ` Philip Blundell
2001-01-22 7:00 ` Jens-Christian Lache
2001-04-01 0:00 ` Jens-Christian Lache
2001-04-01 0:00 ` Philip Blundell
2001-01-22 3:22 ` Richard Earnshaw
2001-04-01 0:00 ` Richard Earnshaw
2001-04-01 0:00 ` Jens-Christian Lache
2001-04-01 0:00 ` Philip Blundell
2001-04-01 0:00 ` David Korn
-- strict thread matches above, loose matches on Subject: below --
2001-01-23 9:21 Jens-Christian Lache
2001-01-23 9:29 ` Philip Blundell
2001-04-01 0:00 ` Philip Blundell
2001-04-01 0:00 ` Jens-Christian Lache
2001-01-22 7:08 Yves Rutschle
2001-04-01 0:00 ` Yves Rutschle
2001-01-22 4:27 Yves Rutschle
2001-01-22 4:41 ` Jens-Christian Lache
2001-04-01 0:00 ` Jens-Christian Lache
2001-01-22 13:38 ` Philip Blundell
2001-01-23 2:18 ` Richard Earnshaw
2001-01-23 2:26 ` Philip Blundell
2001-04-01 0:00 ` Philip Blundell
2001-04-01 0:00 ` Richard Earnshaw
2001-04-01 0:00 ` Philip Blundell
2001-04-01 0:00 ` Yves Rutschle
2001-01-22 3:45 Yves Rutschle
2001-01-22 3:58 ` Jens-Christian Lache
2001-04-01 0:00 ` Jens-Christian Lache
2001-01-22 4:07 ` Jens-Christian Lache
2001-04-01 0:00 ` Jens-Christian Lache
2001-01-22 4:37 ` Jens-Christian Lache
2001-04-01 0:00 ` Jens-Christian Lache
2001-04-01 0:00 ` Yves Rutschle
[not found] <718D38CAB6E0D011B2C90060970C28A56425F0@EXCHANGESERVER>
2001-01-19 2:49 ` Jens-Christian Lache
2001-04-01 0:00 ` Jens-Christian Lache
2001-01-19 2:21 Jens-Christian Lache
2001-01-19 2:58 ` Pierre Saucourt-Harmel (r54698)
2001-04-01 0:00 ` Pierre Saucourt-Harmel (r54698)
2001-04-01 0:00 ` Jens-Christian Lache
2001-01-19 1:56 David Korn
2001-04-01 0:00 ` David Korn
2001-01-18 15:43 Hua Ji
2001-01-18 22:35 ` Helmut Kolb
2001-01-19 3:13 ` Kai Ruottu
2001-04-01 0:00 ` Kai Ruottu
2001-04-01 0:00 ` Helmut Kolb
2001-04-01 0:00 ` Hua Ji
2001-01-18 9:27 Sascha Andres
2001-01-18 13:39 ` Jonathan Larmour
2001-04-01 0:00 ` Jonathan Larmour
2001-01-18 15:23 ` Gerrit Peter Haase
2001-01-22 0:19 ` Sascha Andres
2001-01-22 2:43 ` Jens-Christian Lache
2001-04-01 0:00 ` Jens-Christian Lache
2001-04-01 0:00 ` Sascha Andres
2001-04-01 0:00 ` Gerrit Peter Haase
2001-04-01 0:00 ` Sascha Andres
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=E14KGiw-00062j-00@kings-cross.london.uk.eu.org \
--to=philb@gnu.org \
--cc=crossgcc@sources.redhat.com \
--cc=dfeustel@mindspring.com \
--cc=dkorn@pixelpower.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).