libXaw3d: optional features

2011-08-27 Thread Rafał Mużyło
First a minor nitpick about "Use AM_YFLAGS and BUILT_SOURCES rather than EXTRA_DIST" patch: while BUILT_SOURCES is probably the correct solution there, AM_YFLAGS are redundant, it's already handled elsewhere. Now, for the question about optional features. Frankly, that part isn't really working at

Re: libXaw3d: optional features

2011-08-28 Thread Rafał Mużyło
On Sat, Aug 27, 2011 at 08:46:40PM -0400, Gaetan Nadon wrote: > On Sat, 2011-08-27 at 19:35 +0200, Rafał Mużyło wrote: > > > First a minor nitpick about "Use AM_YFLAGS and BUILT_SOURCES rather > > than > > EXTRA_DIST" patch: > > while BUILT_SOURCE

Re: libXaw3d: optional features

2011-08-28 Thread Rafał Mużyło
On Sun, Aug 28, 2011 at 10:15:05AM -0400, Gaetan Nadon wrote: > > "AM_YFLAGS is usually used to pass the -d option to yacc. > Automake knows what this means and will automatically adjust its rules > to update and distribute the header file built by ‘yacc -d’." > > > ./con

Re: libXaw3d: optional features

2011-08-29 Thread Rafał Mużyło
On Mon, Aug 29, 2011 at 05:16:03AM -0400, Thomas Dickey wrote: > On Mon, 29 Aug 2011, Rafa?~B Muży?~Bo wrote: > > > I can't say that I've used yacc, but 'bison -y -Wall' doesn't print any > > compatibility warnings about '%defines', so it should have been OK. > > It's bison-specific, as you might

[PATCH:libXaw3d] Make laygram.y compatible with bison 2.3 and older

2011-09-04 Thread Rafał Mużyło
Well, I've put all the LayYY stuff there due to 'nm -C -D' output - that's the place where you see the difference between setting the prefix and leaving the default one. Also, you've probably didn't check the resulting lib with 'ldd -r' - it would have complained due to Layout.c. As I already ment