From: fche@redhat.com (Frank Ch. Eigler)
To: Stefano Gallina <warx_sg@yahoo.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: Sid for Windows ! HELP
Date: Thu, 09 Jan 2003 18:28:00 -0000 [thread overview]
Message-ID: <o5znqaw53e.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <20030109084355.57100.qmail@web41113.mail.yahoo.com>
Stefano Gallina <warx_sg@yahoo.com> writes:
> I have been advised to use SID for simulating a
> device, but i was wonderig if SID is available for
> Windows too [...]
Like Robert said, we don't post sid binaries, and even if we did, they
may not be useful for your specific purpose. sid doesn't include
StrongArm2 (xscale) specialized models for the CPU. How badly would
you want it?
- FChE
next prev parent reply other threads:[~2003-01-09 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 8:44 [ECOS] " Stefano Gallina
2003-01-09 10:00 ` Robert Cragie
2003-01-09 18:28 ` Frank Ch. Eigler [this message]
2003-01-16 10:24 ` [ECOS] Building SID for Linux and for Windows -- HELP Stefano Gallina
2003-01-16 10:47 ` Gary D. Thomas
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=o5znqaw53e.fsf@toenail.toronto.redhat.com \
--to=fche@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=warx_sg@yahoo.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).