From: Claudio Bley <bley@CS.uni-magdeburg.de>
To: gcc-help@gcc.gnu.org
Subject: Re: bits/fpos.h missing?
Date: Wed, 30 Jun 2004 11:58:00 -0000 [thread overview]
Message-ID: <20040630115736.GE3347@connect4.urz.uni-magdeburg.de> (raw)
In-Reply-To: <20040630112554.GC3347@connect4.urz.uni-magdeburg.de>
[ Okay, replying to myself. ]
On Wed, Jun 30, 2004 at 01:26:00PM +0200, Claudio Bley wrote:
>
> -fpermissive might help a little. But you're probably better off just
> installing / using GCC 3.1.
Nope, this is obviously wrong as I now tried with the suggested change and
giving the -fpermissive switch esnacc compiled (with a whole bunch of
warning messages, though) with GCC 3.4. YMMV ;-)
Regards.
--
Claudio
prev parent reply other threads:[~2004-06-30 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 10:47 phongphop Mongkolpiyathana
2004-06-30 11:27 ` Claudio Bley
2004-06-30 11:58 ` Claudio Bley [this message]
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=20040630115736.GE3347@connect4.urz.uni-magdeburg.de \
--to=bley@cs.uni-magdeburg.de \
--cc=gcc-help@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).