X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: "Juan Manuel Guerrero" <st001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De>
Organization: Darmstadt University of Technology
To: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Date: Wed, 20 Feb 2002 18:33:57 +0100
Subject: Re: bison and djgpp.env
CC: djgpp-workers AT delorie DOT com
In-reply-to: <10202192134.AA14857@clio.rice.edu>
References: <1676-Tue19Feb2002213757+0200-eliz AT is DOT elta DOT co DOT il> from "Eli Zaretskii" at Feb 19, 2002 09:37:58 PM
X-mailer: Pegasus Mail for Windows (v2.54)
Message-ID: <278A40F3FB0@HRZ1.hrz.tu-darmstadt.de>
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

On Tue, 19 Feb 2002, Charles Sandmann wrote:
> > > [bison]
> > > +BISON_HAIRY=%DJDIR%/lib/bison.hai
> > > +BISON_SIMPLE=%DJDIR%/lib/bison.sim
> >
> > A good idea, IMHO.  Please change that in the CVS right away, so at
> >leats v2.04 will DTRT.
>
> There are a few other changes in djgpp.env in cvs.  Should they be
> in the refresh?  Some?  All?
>
> I'd be happy to commit the above fix to cvs if no one does it first.
> It also seems this should be done for ENSCRIPT_LIBRARY

Please make the bison changes. I have no cvs write access and
this change is essential.

It should be noticed that ENSCRIPT_LIBRARY points to the wrong place.
enscript 1.6.1 and enscript 1.6.2 places their files in the canonical places:
        /dev/env/DJDIR/etc for enscript.cfg and
        /dev/env/DJDIR/share/enscript for the AFM fonts.
AFAIK enscript 1.5.0 has been removed from simtel.net, so the ENSCRIPT_LIBRARY
is no longer needed. IMHO this entry should be removed or it should point
to the right place.

OFYI:
Bison ports from 1.29 to 1.33 install their skeleton files in the canonical
place: /dev/env/DJDIR/share/bison and at the same time as bison.{sim, hai} in
/dev/env/DJDIR/lib. This is needed to avoid changes in djgpp.env. Non of these
ports will stop working if the BISON_{SIMPLE, HAIRY} entries are removed from
djgpp.env. They all have been configured with the canonical path.
The only port that may stop working is bison 1.28. But even this port can be
recompiled with it own canonical path. If such an updated port is uploaded
to simtelnet there would be no longer the need of an bison specific entry in
djgpp.env.
If the size of the binaries, due to NLS,  is an issue, then bison 1.32 can be
recompiled and uploaded without NLS and bison 1.33 with NLS. But that is
only a suggestion.

Regards,
Guerrero, Juan Manuel