When I do a manual/normal install (config/make/install), the "configure" step prints "checking" messages in Terminal. Occasionally, I see something like "resolv.h found, but, can not be compiled..." (the dependency of an installed file that is used in the config & build of the target file). Obviously, the config-process has a way of checking whether or not it can utilize a particular (header-)file. Couldn't something like this be implemented? Say, a little version-test to see if the dep-file is the most current (and CAN be used) and during/after building the "desired" file(s), an actual use-of-the-already-installed-file test? Besides, I would think that if a build would fail, there could then be a warning like "Build Failed! You MUST let PA Get a Newer Version of name-of-file."
After getting several non-compileable resolv.h warnings about missing or incorrect header-files, I looked into the include headers in that file, found and corrected the problem (after researching it, a lot, first). No more resolv.h issues! And, that file is installed with OSX and/or the Developer Tools.
Existing users, log in. New users, create a free account. Lost password?
Why? - dhsanto
When I do a manual/normal install (config/make/install), the "configure" step prints "checking" messages in Terminal. Occasionally, I see something like "resolv.h found, but, can not be compiled..." (the dependency of an installed file that is used in the config & build of the target file). Obviously, the config-process has a way of checking whether or not it can utilize a particular (header-)file. Couldn't something like this be implemented? Say, a little version-test to see if the dep-file is the most current (and CAN be used) and during/after building the "desired" file(s), an actual use-of-the-already-installed-file test? Besides, I would think that if a build would fail, there could then be a warning like "Build Failed! You MUST let PA Get a Newer Version of name-of-file."After getting several non-compileable resolv.h warnings about missing or incorrect header-files, I looked into the include headers in that file, found and corrected the problem (after researching it, a lot, first). No more resolv.h issues! And, that file is installed with OSX and/or the Developer Tools.
Reply to This | Parent
Wednesday, November 15 2006 @ 01:43 PM PST