public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: eCos Disuss <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] eCos w/libstdc++ pthreads exceptions
Date: Tue, 15 Sep 2009 11:55:00 -0000	[thread overview]
Message-ID: <c09652430909150455v41af32e6y85856ad63c9ba962@mail.gmail.com> (raw)

I've updated nios2ecos www.ecosforge.net w/instructions on how to build
a Nios eCos toolchain w/libstdc++ and eCos pthreads exceptions.

These instructions should be of interest to anyone needing a GCC libstdc++
posix threads exceptions eCos toolchain. They are not terribly Nios specific.

http://www.ecosforge.net/ecosforge/trunk/nios2ecos/tools/gcc4libstdxx/simplegcc.txt

The Altera Nios eCos on www.ecosforge.net is a bit rough around
the edges(especially w.r.t. the build scripts, ptf files, etc.), but it works.

Edgar Grimberg just posted some info on some minor new things
that needs to be added to eCos compat/posix to make the GCC
toolchain build a bit more smoothly.

And a GCC toolchain built for Ubuntu can be downloaded here for
those that are interested in taking this for a spin.

http://opensource.zylin.com/gcc/binaries/nios/nios2-elf-gcc-4.1-pthreads-linux.tar.bz2

See http://www.nioswiki.com for source code to GCC(it's part
of the Linux MMU distribution, surprise-surprise...)


Feedback welcome!

-- 
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.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

                 reply	other threads:[~2009-09-15 11:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=c09652430909150455v41af32e6y85856ad63c9ba962@mail.gmail.com \
    --to=oyvind.harboe@zylin.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).