Re: problems compiling oleo-1.99.16

[Pete Wyckoff]

address@hidden said:
> You could have emphasized at the very beginning that I should get 
> (latest) bison.  I had no idea it exists and what it does. Yes, this 
> solves the errors right away. Your patch also fixes it, by the way. I 
> mean: compilation WITHOUT motif (see below)
> 
> So I had/have
> yacc-91.7.30-505
> 
> I just installed:
> bison (GNU Bison) 1.75

I thought I had done so, but also was amazed to see that there
are any non-bison installs around these days.  Oh well.

> It however doesnt want to compile in Xbae. I get now the new error:
> 
> configure:
> checking for Motif... libraries in default path, headers in default path
> checking for Xbae... libraries default path, headers default path
> 
> make:
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I. -I../lib -I../intl     
> -I/usr/X11R6/include -g -O2 -DLOCALEDIR=\"/usr/local/share/locale\" 
> -I/usr/X11R6/include         -DBUILD_PREFIX='"'/usr/local'"' -c lists.c
> In file included from /usr/X11R6/include/X11/Xauth.h:49,
>                 from /usr/X11R6/include/X11/extensions/Print.h:68,
>                 from /usr/X11R6/include/Xm/Xm.h:59,
>                 from io-motif.h:29,
>                 from lists.c:40:
> /usr/X11R6/include/X11/Xfuncs.h:55: warning: `bcopy' redefined
> sysdef.h:53: warning: this is the location of the previous definition
> /usr/X11R6/include/X11/Xfuncs.h:56: warning: `bzero' redefined
> sysdef.h:59: warning: this is the location of the previous definition
> /usr/X11R6/include/X11/Xfuncs.h:57: warning: `bcmp' redefined
> sysdef.h:56: warning: this is the location of the previous definition
> (... and so on ...)

These should be harmless, but annoying.

> Without your patch it finishes with:
> 
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I. -I../lib -I../intl     
> -I/usr/X11R6/include -g -O2 -DLOCALEDIR=\"/usr/local/share/locale\" 
> -I/usr/X11R6/include         -DBUILD_PREFIX='"'/usr/local'"' -c forminfo.c
> /bin/sh ./ylwrap "bison -y" posixtm.y y.tab.c posixtm.c y.tab.h 
> posixtm.h --  -d
> posixtm.y:89.6: parse error, unexpected ":", expecting ";" or "|"
> make[2]: *** [posixtm.c] Error 1
> make[2]: Leaving directory `/home/domi/pack/oleo-1.99.16/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/domi/pack/oleo-1.99.16'
> make: *** [all-recursive-am] Error 2

Recent bison versions are picky about a missing semicolon.  I'll
definitely check in the patch.  Don't try without it.

> If I use your patch it ends with this:
> 
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I. -I../lib -I../intl     
> -I/usr/X11R6/include -g -O2 -DLOCALEDIR=\"/usr/local/share/locale\" 
> -I/usr/X11R6/include         -DBUILD_PREFIX='"'/usr/local'"' -c io-motif.c
> io-motif.c:84: cups/cups.h: No such file or directory
> make[2]: *** [io-motif.o] Error 1
> make[2]: Leaving directory `/home/domi/pack/oleo-1.99.16/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/domi/pack/oleo-1.99.16'
> make: *** [all-recursive-am] Error 2
> 
> There is no CUPS mentioned in configure?

But your configure log thinks it found libcups:

    checking for cupsGetPrinters in -lcups... yes

Maybe it doesn't bother trying to figure out where the include file
resides.

> I would prefer to focus on more elegant solution. what about the first 
> one (without your patch, unless you really need changes in your sources)
> 
> Important question:
> Is oleo still evolving? has it already reached the heights? or is it 
> abandoned?

The patch I sent only address the link problem you were having due to
multiply defined symbols in some of the YACC files.  Everything else in
the make log you sent compiled fine, including lists.c.  But you must
have reconfigured to use motif and now that is causing problems.

Personally I don't use the motif interface:  "--without-motif".
If you (or anyone reading) has time to clean up the motif configure
issues and make it compile properly, I'd happily make sure the work got
put into the distribution.  The cups issue is probably just a matter
of adding a configure check for the header file and disabling it if
not found.  You could edit config.h to force it off too.

I use the straight X version once a year for about a solid week figuring
out the taxes, and am pretty confident that most of the spreadsheet
features work fine.  But there is no recent active work to add more
features or to change the GUI.  Some of us maintain it for fun, as you
have found out here.

                -- Pete