Re: Latest Gnomehide RPM issues

["Lee J. Moore" <mlist strictlybritish com>]

On Tue, 2002-01-08 at 22:38, Havoc Pennington wrote:
> 
> "Lee J. Moore" <mlist strictlybritish com> writes:
> > 
> > After trying to update Gnomehide with the rpms released earlier today, I
> > found that the ati-spi, gail & and eel2 rpms are no longer linked
> > against various new libraries.
> >
> 
> Thanks, I forgot to rebuild these packages so they are still linked to
> the old packages.

No problem. Btw, regarding the at-spi-0.0.3.90 SRPM.  I'm not sure
whether there is a genuine problem with the source or whether I should
have installed more up to date (rawhide?) libraries before attempting to
build it, but I thought I'd post some of the error text from the make
failure.

gcc -DHAVE_CONFIG_H -I. -I. -I.. -I .. -I .. -DORBIT2=1
-I/usr/include/bonobo-activation-2.0 -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/include/orbit-2.0
-I/usr/include/linc-1.0 -I/usr/include/libxml2
-I/usr/include/libbonobo-2.0 -I/usr/include/atk-1.0
-I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include
-I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/include/freetype2
-g -O2 -c accessible.c  -fPIC -DPIC -o accessible.lo
In file included from ../libspi/libspi.h:32,
                 from accessible.c:27:
../libspi/hypertext.h:45: parse error before
`POA_Accessibility_Hypertext__epv'
../libspi/hypertext.h:45: warning: no semicolon at end of struct or
union
In file included from ../libspi/libspi.h:35,
                 from accessible.c:27:
../libspi/selection.h:45: parse error before
`POA_Accessibility_Selection__epv'
../libspi/selection.h:45: warning: no semicolon at end of struct or
union
make[2]: *** [accessible.lo] Error 1
make[2]: Leaving directory
`/usr/src/redhat/BUILD/at-spi-0.0.3.90/libspi'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/redhat/BUILD/at-spi-0.0.3.90'
make: *** [all-recursive-am] Error 2

I've taken a quick (emphasis on 'quick'!) glance at accessible.c,
libspi.h, hypertext.h and hypertext.c and can't notice any obvious
problems.  Certainly none related to the compiler warnings.

Best regards

Lee J. Moore