On Wed, Sep 3, 2014 at 9:30 AM, Stephan Kulow <coolo@suse.de> wrote:
On 03.09.2014 16:21, Archie Cobbs wrote:
On Wed, Sep 3, 2014 at 2:43 AM, Bernhard Voelker <mail@bernhard-voelker.de> wrote:
From your build log:
[ 157s] checking for logger... no [ 157s] configure: error: logger not found
I'm far from being an expert on this, and I don't know twilio-utils, but why would a package need a logger at *build time*?
This is a very common portability trick: locate a utility via AC_PATH_PROG() at build time, instead of making non-portable assumptions about its location that will only fail at runtime.
logger(1) is a perfect example - e.g. it could be in /bin/logger or /usr/bin/logger, and in openSUSE it's in fact in both locations (with a symlink), but on other Linux systems... who knows?? Hence the use of AC_PATH_PROG() to find it at build time.
Well, if your configure can find it in $PATH, your exec is most likely to do the same.
Yeah - that's the whole point :) In any case, it is the reverse situation which is more critical. If you DON'T check for it at build time, then if it's NOT there you'll only discover the error at runtime. With the ./configure test, you discover the problem at build time instead. This is the whole point of using ./configure - figure out where stuff is at build time (or figure out that stuff can't be found and report an error), so that the following assertion is true: IF the thing builds successfully, THEN it will work properly at runtime - no matter what O/S you build it on. -Archie -- Archie L. Cobbs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org