From: "Mark E." <snowball3 AT bigfoot DOT com>
To: gcc AT gcc DOT gnu DOT org, djgpp-workers AT delorie DOT com
Date: Mon, 17 Jul 2000 15:07:16 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: GCC headers and DJGPP port
Message-ID: <39732124.29932.12D387@localhost>
In-reply-to: <39734D95.6D145F00@softhome.net>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> Mike Stump wrote:
> > A sure sign of a non-maintained port, is a system with its own
> > vararg.h...
> 
> Or is it a sign of system which had its own little GCC fork previously?

Which we're actively trying to eliminate now. But when patches to close this 
gap go undealt with while others are quickly handled, it is tempting to think 
the maintainers aren't inclined to help eliminate the gap. 

Mark