From: Andrew Lunn <andrew@lunn.ch>
To: James Yates <j.yates@quartzuk.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Problems with test
Date: Tue, 14 Oct 2003 11:43:00 -0000 [thread overview]
Message-ID: <20031014114305.GB22392@lunn.ch> (raw)
In-Reply-To: <CB39E7B8FC98924D85DFBED207E4CC9831F8F0@ip02.quartzelec.adsl.gxn.net>
> I am reasonably sure I am using the latest version of the sh-elf-gcc
> which is 3.2.1 which I downloaded from cygwin last week. Has anyone
> come across this problem, or has any ideas what could be wrong. I
> was also getting a seg fault when building snmp which is why I have
> taken networking out.
Have you tried the compiler recommended by eCosCentric? There version
has been tested with eCos and should work fine.
See http://ecos.sourceware.org/ecos/getstart.html, section toolchain.
Andrew
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-10-14 11:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 11:31 James Yates
2003-10-14 11:43 ` Andrew Lunn [this message]
2003-10-14 14:30 James Yates
2003-10-14 15:09 ` Andrew Lunn
2003-10-15 8:35 James Yates
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=20031014114305.GB22392@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@sources.redhat.com \
--cc=j.yates@quartzuk.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).