From: 520065607613-0001@t-online.de (Frank Pilhofer)
To: gcc@gnu.org
Subject: Successful compilation of Mico using gcc snapshot
Date: Fri, 30 Nov 2001 08:34:00 -0000 [thread overview]
Message-ID: <20011130172149.H508@rose.fpx.de> (raw)
Message-ID: <20011130083400.XqmIeJBP-49iCz4EPRqRveHydKb1Z-etF4_shD1OSXM@z> (raw)
Hi folks,
I have noticed that bug # 3145, which in the past caused runtime errors
in Mico (and all other ORBs that I know of), has been fixed. And indeed I
have succeded in using the November 26 snapshot to build and run Mico.
Good work, everybody.
Now I'm hoping that there will be a gcc release that includes this patch
before we get swamped with angry users who're failing to compile Mico with
their favorite Linux distribution's compiler. I will have to wait until
gcc 3.1, won't I?
Compilation with gcc 3 seems much slower than with gcc 2.95, but in any
case I prefer a correct compiler over a fast one.
Frank
--
Frank Pilhofer ........................................... fp@fpx.de
Isn't it amazing how political candidates can give you all their good
points and qualifications in a thirty-second TV commercial? - A. E.
Neuman
next reply other threads:[~2001-11-30 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-23 2:22 Frank Pilhofer [this message]
2001-11-30 8:34 ` Frank Pilhofer
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=20011130172149.H508@rose.fpx.de \
--to=520065607613-0001@t-online.de \
--cc=gcc@gnu.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).