From: Axel Kittenberger <Axel.Kittenberger@maxxio.at>
To: Toon Moene <toon@moene.indiv.nluug.nl>
Cc: gcc@gcc.gnu.org
Subject: Re: How to understand gcc
Date: Tue, 18 Dec 2001 23:27:00 -0000 [thread overview]
Message-ID: <200112190720.IAA21264@merlin.gams.co.at> (raw)
In-Reply-To: <3C1FC65D.EE8AEF55@moene.indiv.nluug.nl>
On Tuesday 18 December 2001 23:42, Toon Moene wrote:
> Axel Kittenberger wrote:
> > Well that much of an arcane art how some people view compiler aren't the
> > translors.
>
> PARSE ERROR AT OR NEAR LINE 1.
> NO OBJECT PRODUCED.
> COMPILATION ABORTED.
Oh well , I'm sorry got it messed up a bit :o)
Don't you have error correction? *g*
- Axel
next prev parent reply other threads:[~2001-12-19 7:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 15:46 mike stump
2001-12-17 16:20 ` David Rasmussen
2001-12-18 2:59 ` Axel Kittenberger
2001-12-18 15:03 ` Toon Moene
2001-12-18 15:39 ` Neil Booth
2001-12-18 23:27 ` Axel Kittenberger [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-18 17:32 mike stump
2001-12-17 15:01 David Rasmussen
2001-12-17 15:05 ` Neil Booth
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=200112190720.IAA21264@merlin.gams.co.at \
--to=axel.kittenberger@maxxio.at \
--cc=gcc@gcc.gnu.org \
--cc=toon@moene.indiv.nluug.nl \
/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).