From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Subject: GCC configure buglet
Date: Mon, 19 May 2003 21:03:59 +0200
Message-ID: <000001c31e39$67cd9000$2302a8c0@dualzastai>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Reply-To: djgpp-workers AT delorie DOT com

Since gcc 3.3 is being discussed anyway, could whoever acts
as DJGPP maintainer for gcc (DJ I believe) take another look
at gcc bug bootstrap/3867?

That (rather old) bug report relates to a check in configure
that looks for a compiler/assembler bug using ELF-specific
assembly (i.e. with section attributes and .4byte pseudo-ops);
this causes it to incorrectly flag DJGPP as having the error.

This still seems to be present in gcc 3.3.  The problem report
contains a rather hackish patch I cobbled together at the time;
with that patch, configure DTRT both on Linux and DJGPP (the
only platforms I had access to).

Not exactly a blocker (I have no idea if this has any _real_
impact, but this can and should be fixed IMHO (at the very least
in the DJGPP packages).