From: "Ling Su" <lingsu@palmmicro.com>
To: "Jonathan Larmour" <jlarmour@redhat.com>,
"Lewin A.R.W. Edwards" <larwe@larwe.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] How to run eCos in SMDK41100 board
Date: Wed, 31 Jan 2001 01:04:00 -0000 [thread overview]
Message-ID: <00d101c08b65$0be8d560$0301a8c0@leopard> (raw)
In-Reply-To: <4.3.2.7.2.20010130234158.00b05360@larwe.com>
>
> >Ah, that's a mistake then. Mentioning that snapshot date was included by
> >accident because it was a boilerplate.
>
> Argh!
>
> > > different. (The stackalign.pat doesn't apply either, or at least
didn't for
> > > me).
> >
> >Mentioning that checkout date was the mistake, that's all. Using a recent
> >snapshot should result in much better behaviour. And the descripion of
> >stackalign.pat does say it doesn't apply for snapshots after 2000-03-13.
>
> However, the web page does say that it is applicable to snaps up to and
> including 20000313!! Please fix that too.
>
I thought the same problems applied on vrc4373 environment, I followed the
instructions to build a cross compiler for vr4300 by using snapshot
20000313, I didn't find a stable way to do it in Window2000 environment. I
failed when I update to a new version cygwin. I can not find a simple rule
to follow, so at last I quit it and move it Linux. It is working always.
-Ling
prev parent reply other threads:[~2001-01-31 1:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 18:42 james chen
2001-01-30 19:04 ` Jonathan Larmour
2001-01-30 19:45 ` james chen
2001-01-30 19:50 ` Jonathan Larmour
2001-01-30 19:54 ` Lewin A.R.W. Edwards
2001-01-30 20:05 ` Jonathan Larmour
2001-01-30 20:11 ` Lewin A.R.W. Edwards
2001-01-30 20:14 ` Jonathan Larmour
2001-01-30 20:19 ` Lewin A.R.W. Edwards
2001-01-30 20:24 ` Jonathan Larmour
2001-01-30 20:30 ` Lewin A.R.W. Edwards
2001-01-30 20:41 ` Jonathan Larmour
2001-01-30 20:43 ` Lewin A.R.W. Edwards
2001-01-31 1:04 ` Ling Su [this message]
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='00d101c08b65$0be8d560$0301a8c0@leopard' \
--to=lingsu@palmmicro.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@redhat.com \
--cc=larwe@larwe.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).