delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | kendall.sfbr.org: jeffw set sender to jeffw AT darwin DOT sfbr DOT org using -f |
Date: | Wed, 19 Sep 2001 11:49:57 -0500 |
From: | JT Williams <jeffw AT darwin DOT sfbr DOT org> |
To: | djgpp-workers AT delorie DOT com |
Subject: | Re: Bison assertion failure on libc sources |
Message-ID: | <20010919114957.B22205@kendall.sfbr.org> |
References: | <20010916101003 DOT 23685 DOT qmail AT softhome DOT net> <796A27E5802 AT HRZ1 DOT hrz DOT tu-darmstadt DOT de> |
Mime-Version: | 1.0 |
User-Agent: | Mutt/1.2.5i |
In-Reply-To: | <796A27E5802@HRZ1.hrz.tu-darmstadt.de>; from ST001906@HRZ1.HRZ.TU-Darmstadt.De on Wed, Sep 19, 2001 at 05:01:06PM +0200 |
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 |
-: 2) The parser files bison.simple and bison.hairy will be placed -: in %DJDIR%/lib too. Now they will be available as bison.simple -: and bison.hairy in their canonical place, %DJDIR%/share/bison, -: and in their DJGPP 2.03 specific place as bison.sim and bison.hai. Perhaps this should be done only for this combination of bison and djgpp; subsequent versions of bison would place these files only in their canonical location, and subsequent versions of djgpp would remove the [bison] section. I understand that these sorts of things can generate lots of FAQs, but I feel strongly that bringing djgpp ports into full Un*x compliance (wherever possible, and over a suitable transition period) is A Good Thing.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |