[fetchmail]configuring in a different directory

I configured in a different directory than source
(redhat i386 6.2)

During configure, I get a whole bunch of:

-- makedepend: warning:  unmime.c, line 15: cannot find include file
"config.h"
        not in config.h
        not in config.h
        not in /usr/local/lib/gcc-include/config.h
        not in /usr/include/config.h
        not in /usr/lib/gcc-lib/i386-linux/2.7.2.1/include/config.h
makedepend: warning:  xmalloc.c, line 8: cannot find include file
"config.h"
        not in config.h
        not in config.h
        not in /usr/local/lib/gcc-include/config.h
        not in /usr/include/config.h
        not in /usr/lib/gcc-lib/i386-linux/2.7.2.1/include/config.h

The last path is very strange, since I'm using
: leisner(_at_)soyata;gcc -v
Reading specs from
/usr/gnu/gcc-2.95.2/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/specs
gcc version 2.95.2 19991024 (release)

Also, when trying to make, I get this:
gcc -L/usr/kerberos/lib -L/usr/kerberos/lib  rcfile_y.o rcfile_l.o
socket.o getpass.o pop2.o pop3.o imap.o etrn.o odmr.o fetchmail.o idle.o
env.o options.o daemon.o driver.o sink.o rfc822.o smtp.o xmalloc.o uid.o
mxget.o md5ify.o cram.o kerberos.o gssapi.o opie.o rpa.o interface.o
netrc.o base64.o error.o unmime.o conf.o checkalias.o smbdes.o
smbencrypt.o smbmd4.o smbutil.o ipv6-connect.o lock.o  md5c.o  -lkrb4
-ldes425 -lcrypt  -lresolv -lkrb5 -lk5crypto -lcom_err  -lfl -o
fetchmail
make -C po
make[1]: Entering directory `/usr/local/obj/fetchmail-5.8.1/po'
make[1]: *** No rule to make target
`/usr/local/src/networks/fetchmail-5.8.1/rcfile_y.c', needed by
`/usr/local/src/networks/fetchmail-5.8.1/po/fetchmail.pot'.  Stop.
make[1]: Leaving directory `/usr/local/obj/fetchmail-5.8.1/po'
make: *** [po] Error 2

I'm not yet on this list, so make sure I get a copy...

I'm configuring a new sendmail since I think I want to do some work...

I want to limit the number of children I spawn at one time...
(i.e. add one for each sendmail, subtract one for each child reaped, up 
to a limit).

I don't think you can currently do that..should be easy to implement
(i.e. I don't want to see hundreds of children running).
Does the -b (batchlimit) have any effect on the number of children
spawned?


marty
leisner(_at_)rochester(_dot_)rr(_dot_)com  
The Feynman problem solving Algorithm
        1) Write down the problem
        2) Think real hard
        3) Write down the answer
                Murray Gell-mann in the NY Times