On 12 Jun 2001 10:54:53 -0400, Adam D. Gorski wrote:
> Recently, I guess that would be last week or so, my routine compilation of
> the latest CVS failed.
There can be problems, because I drastically remove stuff which seems
useless, but it can cause problems, because I cannot test all cases if
they still work.
> The problem exists in gtkfunc.c where timeval struct
> is declared (line 156). The error I got is that basically timeval is
> undeclared. I fixed this by including sys/time.h in gtkfunc.c and everything
> compiled fine.
Different compilers need different includes, so please report all such
compilation problems. I have removed/changed lots of includes yesterday,
so I may have broken something on some machines. Please try especially
if you have gcc 3.0 -- it reports more warnings.
> I just updated to the latest CVS (it's Tuesday, 10:47 am) and
> I actually did a clean CVS download since there were a lot of changes and I
> wanted to see if that gtkfunc problem got fixed. Well, I got the same error
> message as before so, once again, I included that header file and all
> compiled fine..
Maybe no one knew about that problem so it wasn't fixed of course :)
I have just commited the fix you suggested.
> BUT.. now when I try to start gnomeicu I get this error and
> a segfault
> ** WARNING **: file applet-widget.c: line 907: Corba Exception: type = 2
> exid = IDL:CORBA/BAD_PARAM:1.0
> ** WARNING **: Cannot start CORBA
> Now I'm not sure if this is my fault somehow, but I figured I'd better
> report it.
No, it's MY problem. I changed that stuff yesterday, but it didn't help.
I don't know how to detect if applet was started sucessfully or not, and
how to avoid the nasty behavior when launching gnomeicu also launches a
panel. I want to start without applet if panel does not exist.
> So basically I don't know if the gtkfunc.c problem is an actual
> code problem or if it's just my box, and I don't know why the program is
> segfaulting on start now. Any help/info would be appreciated. Thanks!
I have fixed both of these problems now (June 12, 23:30 +0200), at least
to the state it was earlier.