Re: Problems compiling on Solaris 2.8 w/ gcc 2.95.2

[Danny Backx]

Thomas Boyda wrote:
> I just tried to compile oleo-1.99.16 and I got the following problems:

> In solaris 2.8 "/usr/include/libintl.h line 33 gettext is defined:
> extern char *gettext(const char *);
> 
> I hacked around that by changing the declaration to const char * in
> src/io-term.c.

Good. This type of stuff is hard to catch in a system-independent manner.

> ld: fatal: symbol `yys' is multiply defined:
>         (file parse.o and file posixtm.o);
> ld: fatal: symbol `yyv' is multiply defined:
>         (file parse.o and file posixtm.o);
> ld: fatal: File processing errors. No output written to oleo

> I didn't see an easy hack around this.

The easy answer for me would be to say toss Sun's yacc and use bison instead.

I really don't know the hard answer though, but this has something to do with
the programs generated by yacc. Look at "man yacc", maybe it has an option
to prevent generating this type of stuff.

In case the above doesn't ring a bell, yacc is a tool that you can use to
generate parser programs. There are several such pieces in Oleo, the sources
to yacc are the *.y files. The code output by yacc is obviously not meant to
work in an environment where one applications contains more than one such
yacc-generated piece.

You have a chance that you can tell yacc to generate something that does
allow this, the other option would be to use bison, which is a GNU
equivalent to yacc.

Please ask further if this doesn't help.

        Danny
-- 
Danny Backx (address@hidden address@hidden)
Home page :     http://users.skynet.be/danny.backx
Projects:       LessTif (http://www.lesstif.org)
                Oleo    (http://www.gnu.org/software/oleo/oleo.html)