Hi.

I was trying to compile GNOME 2.0 on a freebsd current
machine on which the world was recently cvsuped, built
and installed. CVSUP-ed on 09/22/2002

the gnome compilation breaks while trying to compile
libgtop2. here is the error:


cc -DHAVE_CONFIG_H -I. -I. -I../.. -D_IN_LIBGTOP -D_GNU_SOURCE
-DGLIBTOP_NAMES -I../.. -I../.. -I../../sysdeps/freebsd -I../../include
-DNEED_GNOMESUPPORT_H -I../../support -I../../support
-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -O -pipe
-mcpu=pentiumpro -I/usr/X11R6/include
-DGTOPLOCALEDIR=\"/usr/local/share/locale\" -DLIBGTOP_VERSION=\"2.0.0\"
-DLIBGTOP_SERVER_VERSION=\"5\" -DLIBGTOP_VERSION_CODE=2000000
-DLIBGTOP_SERVER=\"/usr/local/bin/libgtop_server2\" -I/usr/local/include
-O -pipe -mcpu=pentiumpro -c proctime.c  -fPIC -DPIC -o .libs/proctime.lo
In file included from ../../glibtop.h:33,
                 from proctime.c:24:
glibtop_machine.h:59:8: warning: extra tokens at end of #endif directive
proctime.c: In function `calcru':
proctime.c:76: structure has no member named `p_kse'
proctime.c:77: structure has no member named `p_kse'
proctime.c:78: structure has no member named `p_kse'
gmake[3]: *** [proctime.lo] Error 1
gmake[3]: Leaving directory
`/usr/ports/devel/libgtop2/work/libgtop-2.0.0/sysdeps/freebsd'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory
`/usr/ports/devel/libgtop2/work/libgtop-2.0.0/sysdeps'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/devel/libgtop2/work/libgtop-2.0.0'
gmake: *** [all-recursive-am] Error 2
*** Error code 2

Stop in /usr/ports/devel/libgtop2.
*** Error code 1

Stop in /usr/ports/x11/gnomeapplets2.
*** Error code 1

Stop in /usr/ports/x11/gnome2.

=============================================================

I was wondering if anyone else has tried to compile this
successfully?? or if somebody more familiar with this
error could help me fix it!!

Thanks and best regards to all
Saurabh Gupta


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to