Yaakov S wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Gerrit P. Haase wrote:
$ cygcheck -f /bin/pidof
sysvinit-2.84-4
This should be included in setup hint then.
Would you mind adding it to GConf2's requires? I use this script
whenever a GConf schema is installed, in order to assure that gconfd-2
will start successfully, which means killing it and clearing it's lock.
No problem, I think this is the best solution.
You commented the winsock.h check because configure chokes.
I get an similar error from configure when it test for resolv.h,
therefore I use a .m4 snippet which does real resolv.h checking.
For me I get HAVE_RESOLV_H 0 in config.h without it.
Maybe it was already fixed in the latest release?
$ cygcheck /usr/bin/cygORBit-2-0.dll
...
C:/cygwin/bin\cygminires.dll
So it seems minires is pulled in. What happens when you build my package?
I have not tried to build it yet. Volker reported only problems with
the docs.
checking for arpa/nameser.h... yes
checking resolv.h usability... no
checking resolv.h presence... yes
configure: WARNING: resolv.h: present but cannot be compiled
configure: WARNING: resolv.h: check for missing prerequisite headers?
configure: WARNING: resolv.h: see the Autoconf documentation
configure: WARNING: resolv.h: section "Present But Cannot Be Compiled"
configure: WARNING: resolv.h: proceeding with the preprocessor's result
configure: WARNING: resolv.h: in the future, the compiler will take
precedence
configure: WARNING: ## ------------------------------------------ ##
configure: WARNING: ## Report this to the AC_PACKAGE_NAME lists. ##
configure: WARNING: ## ------------------------------------------ ##
checking for resolv.h... yes
It seems that the result is yes anyway... however I don't like seeing
things like this in the log. Including a check for resolv.h which
actually works doesn't harm and may also be submitted upstream while
someone else tries to include it in future autoconf releases.
Gerrit
