Date: Tue, 2 Jan 2001 10:58:28 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Jean Michel <jmichel AT schur DOT institut DOT math DOT jussieu DOT fr>
cc: djgpp AT delorie DOT com
Subject: Re: Bug in djgpp libc
In-Reply-To: <92qorb$1c4$1@schur.institut.math.jussieu.fr>
Message-ID: <Pine.SUN.3.91.1010102105812.18307E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On 1 Jan 2001, Jean Michel wrote:

> The suggestions  you made imply put  some ifdefs in the  ruby source for
> this particular port. I  am not a ruby developer, but  I get the feeling
> this port  is not very  popular anyway (Cygwin  one is more  popular) so
> people may  just stop supporting the  djgpp port if too  many ifdefs are
> needed...

The suggestions I made are quite simple.  I doubt if you'd need more
than a single #ifdef'ed fragment to implement any of them.  In my
experience with maintainers of various packages, a clean patch with a
well explained reason will not be rejected in most cases.