From: "Ling Su" <lingsu@palmmicro.com>
To: "Jonathan Larmour" <jlarmour@redhat.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Regarding to eCos on VRC4373
Date: Wed, 10 Jan 2001 00:19:00 -0000 [thread overview]
Message-ID: <011e01c07ade$44779570$0301a8c0@leopard> (raw)
In-Reply-To: <3A5BB04A.38F502F8@redhat.com>
> > After previous struggle, I can work with eCos on the VRC4373 board in
Linux
> > environment. Since some new members just joined the team, and not all of
> > them love Linux platform that much, I need to figure out a way for them
in
> > WindowsNT/2000. Currently I have some questions, please refer following,
> >
> > <1>. After compiling egcs snapshot in Windows environment, during
> > compilation, it also complains "xxx.h is shorter than expected...".
What's
> > wrong with that? How to eliminate them? It is really anonoying.
>
> We would need more details of the error than that.
>
I have prepare a more detailed information for this later.
I tried the newest snapshot of gcc for VR4300 processor, unfortunately the
patch available on VRC4373 developments tools webpage are all obselete. I
tried to apply them, a lot of failures, any newer version gcc has been
tested except the snapshot20000313 version?
Best Regards,
-Ling
next prev parent reply other threads:[~2001-01-10 0:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 14:59 Ling Su
2001-01-09 16:44 ` Jonathan Larmour
2001-01-09 23:37 ` Ling Su
2001-01-10 3:30 ` Nick Garnett
2001-01-10 5:15 ` [ECOS] assertion checks for stack Joerg Rapka
2001-01-10 9:10 ` [ECOS] Regarding to eCos on VRC4373 Jonathan Larmour
2001-01-10 0:19 ` Ling Su [this message]
2001-01-10 9:08 ` Jonathan Larmour
[not found] ` <005e01c07ad5$5ba58210$0301a8c0@leopard>
2001-01-10 9:17 ` Jonathan Larmour
2001-01-10 14:08 ` Ling Su
2001-01-10 14:17 ` Jonathan Larmour
2001-01-10 15:45 ` Grant Edwards
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='011e01c07ade$44779570$0301a8c0@leopard' \
--to=lingsu@palmmicro.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@redhat.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).