Geoff The same errors remain at the end. The last few lines of the make follow:- Comments continue after gcc -g -O2 -Wall -Wunused -o firestarter firestarter.o util.o logread.o menus.o parse.o druid.o druid-choices.o service.o preference s.o scriptwriter.o modify_ipup.o modrules.o lookup.o savelog.o addrules.o ipchains-script.o netfilter-script.o sort-clist.o portfw.o -rdynamic -lgnomeui -lart_lgpl -lgdk_imlib -lSM -lICE -lgtk -lgdk -lgmodule -lXi -lXext -lX11 -lgnome -lgnomesupport -lesd -laudiof ile -lm -ldb1 -lglib -ldl -rdynamic -L/opt/gnome/lib -L/usr/lib -L/usr/X11R6/lib -rdynamic -lgnorba -lORBitCosNaming -lORBit -lIIOP -lORBitutil -lgnomeui -lart_lgpl -lgdk_imlib -lSM -lICE -lgtk -lgdk -lgmodule -lXi -lXext -lX11 -lgnome -lgnomesupport -lesd -laudio file -lm -ldb1 -lglib -ldl -lpanel_status /usr/i486-suse-linux/bin/ld: cannot find -lesd collect2: ld returned 1 exit status make[3]: *** [firestarter] Error 1 make[3]: Leaving directory `/Download/firestarter/firestarter-0.7.1/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/Download/firestarter/firestarter-0.7.1/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/Download/firestarter/firestarter-0.7.1' make: *** [all-recursive-am] Error 2 On Mon, 19 Nov 2001 08:05:20 +0000, Geoff wrote:
I am not sure *which* errors remain. I don't think it is very likely that the same error you originally posted remains if the docklet-h reference is now resolved. Please let us know whether or not this same error remains.
This error has gone <snip>
Are these the errors you are referring to in your earlier paragraph? If so then does compilation eventually halt with the kind of "make: *** [all -recursive-am] Error " that the absence of docklet-h produced? If there is no such error then you need to be aware that the gcc compiler very often throws out warnings of the kind you quote. They are for the assistance of the programmer and, though they *may* indicate trouble ahead for the user, that is by no means inevitable. Occasionally you can get rid of some or all of them by making sure that you have configured appropriately for your system - running "configure --help" often provides useful information.
As you see the recursive errors are there. If you continue with the install (make install) the program will not run or produce any response.
One way of telling whether any error you see has been fatal (apart from looking for the "make: *** [all-recursive-am] Error" message), is to look and see whether the compiler has produced an executable. Look in the directory in which you untarred the file. Either in that directory or (in the case of more complex programs), in some sub-directory of it (probably /src), you will see an executable (in green if you are using emelfm), which bears the name of the program and a creation date of a minute or two ago. This is the executable that "make install" will subsequently copy to some system-wide /bin. If such a file is present then, as a general rule, compilation succeded.
There are no execs in /scr and in the source directory only 2 have been created, namely config.status & libtool. Don't know if that is a standard file that is produced.
_________________________________________________________
Regards, David