Re: ORBit, OAF fails to compile with gcc 2.95.2

  To do it without patching the source, add "--disable-more-warnings" to
your configure options.  You won't get the -Werror or the warnings,
but you probably don't care as an end-user.

On Wed, Aug 02, 2000 at 10:34:59AM +0200, Remco van de Meent wrote:
> Andy Tai wrote:
> > Hi, this may count as a minor bug.  The latest releases of OAF 0.4.0 
> > fails to compile with gcc 2.95.2, with the following error:
> > 
> > gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I.. -I../liboaf -I../liboaf -I/opt/gnome/installed/lib/glib/include -I/opt/gnome/installed/include -I/opt/gnome/installed/lib/glib/include -I/opt/gnome/installed/include -DVERSION=\"0.4.0\" -O2 -fpermissive -O2 -fpermissive -Wall -Wno-uninitialized -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare -Wsign-promo -Werror -c  -fPIC -DPIC oaf-stubs.c -o oaf-stubs.lo
> > cc1: warnings being treated as errors
> > In file included from /usr/include/string.h:346,
> > 		 from oaf-stubs.c:5:
> > 		 /usr/include/bits/string2.h: In function `__strcpy_small':
> > 		 /usr/include/bits/string2.h:419: warning: pointer of type `void *' used in arithmetic
> > 
> > 
> > It seems gcc does not allow these warnings and refuses to continue.
> > System: Red Hat 6.2 with gcc 2.95.2
> You may want to remove the -Werror flag from the compile options in the
> Makefiles. Maybe this isn't the correct way to solve it, but at least
> it seems to work.
> Cheers,
> Remco.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]