From: "Marc Pignat" <marc.pignat@hevs.ch>
To: <gary@chez-thomas.org>,
<eCos Discussion <ecos-discuss@sources.redhat.com>>
Subject: [ECOS] Rép. : Re: [ECOS] #include <new> in mqueue.cxx
Date: Sun, 14 Jul 2002 23:49:00 -0000 [thread overview]
Message-ID: <sd328c76.063@hevs.ch> (raw)
I've got the same problem with gcc 3.0.4 (for arm-elf)
but gcc 2.95.2 compiles this without problem.
I tried using gcc 3.0.4 to use THUMB code, but I've got some problems...
Marc
=====================================================================
Marc Pignat - Collaborateur Scientifique (Système Intégrés)
Haute Ecole valaisanne
Rte du Rawyl 47
1950 Sion
=====================================================================
Bureau : A306 tél : +41 27 606 8748 fax : +41 27 606 8715 mail : marc.pignat@hevs.ch
Privé : +41 79 678 71 13
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
reply other threads:[~2002-07-15 6:49 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=sd328c76.063@hevs.ch \
--to=marc.pignat@hevs.ch \
--cc=gary@chez-thomas.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).