Mail Archives: djgpp-workers/2000/02/21/04:25:40
On Sun, 20 Feb 2000, Mark E. wrote:
> Perhaps this
> side effect of mkinstalldirs (that you'll get a /dev directory and a env
> directory) with '/dev/env/DJDIR' should be mentioned somewhere?
Probably, but where is the good place to mention this?
> If it doesn't conflict with your todo list, I'd like to upload a
> binutils 2.9.5 beta and perhaps update Bison to 1.28.
How can removing things from my todo list be in conflict with
anything? ;-) And with GDB 5.0 breakage on my back, on top of that?
Please go ahead.
Did you install all my changes to Binutils that I sent to the Binutils
list? If not, I'd like them to be added. They are well tested on my
machines, I'm using the patched Binutils for several months. Some of
the patches are really important bugfixes. Let me know if you need me
to send the patches.
Also, what about the alignment--does your version use 16-byte
alignment of subsections? I think that's what we wanted.
> One thing I'd like to do to is give Bison it the ability to generate
> y.tab.c in LFN mode (kinda like makeinfo and split info files),
> unless overriden by BISION_LFN_OUTPUT. Is this ok with folks and
> will it create any problems?
Generating y.tab.* under LFN is IMHO a good idea, but why do we need
another environment variable to defeat that? Isn't the combination of
-b, -o, and LFN=n flexible enough?
Btw, somebody reported a bug with -b (I think), so it'd be probably a
good idea to fix it while you are at that. I can send you the report,
if you want.
Thanks!
Btw, feel free to ``conflict'' even more with my todo list of pending
ports ;-) The list is long, and I could use all the help I can get.
This goes for everybody on this list and elsewhere.
- Raw text -