From: Grant Edwards <grante@visi.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: NIOS2 toolchain build failure under Cygwin
Date: Tue, 08 Aug 2006 12:57:00 -0000 [thread overview]
Message-ID: <20060808125711.CC44354393@rivatek.dnsalias.net> (raw)
In-Reply-To: <c09652430608080524l2588d2b4ja392ac04ba919b@mail.gmail.com>
In gmane.os.ecos.general, you wrote:
> I believe I'm seing the same segmentation fault.
>
> Did you find a way to resolve this problem?
Sort of: Use Linux.
> My first thoughts was to try to revert to an older GCC version for
> CygWin or worst case attempt a cross-build from Linux.
I just switched to Linux. Once I get everything else ironed
out, I'll mess with Cygwin again (assuming my client really
wants me to).
Building eCos for NIOS2 is the biggest mess I've ever seen: A
Shell script wrapper for a Java program that generates a CDL
file that generates a shell script that generates a Perl script
that calls a Java program that generates include files, etc.
etc.
What a pile.
--
Grant Edwards grante Yow! I HAVE a towel.
at
visi.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-08-08 12:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 12:25 [ECOS] " Øyvind Harboe
2006-08-08 12:57 ` Grant Edwards [this message]
2006-08-09 8:14 [ECOS] " Øyvind Harboe
2006-08-09 13:45 ` Grant Edwards
2006-08-09 14:07 ` Andrew Lunn
2006-08-09 14:31 ` Grant Edwards
2006-08-09 14:55 ` Andrew Lunn
2006-08-09 15:20 ` Bart Veer
2006-08-09 15:58 ` Øyvind Harboe
2006-08-09 16:36 ` Grant Edwards
2006-08-09 20:05 ` Bart Veer
2006-08-09 20:28 ` Øyvind Harboe
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=20060808125711.CC44354393@rivatek.dnsalias.net \
--to=grante@visi.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).