Since I was perusing the libusb-devel list, I just saw the patch below. Looks like a no brainer, so I have committed and pushed it to the libusbx git repository.
Regards, /Pete On 2012.05.14 19:36, Lars Wirzenius wrote: > Previously, there was a naked "exit", which exits with the exit code > of the previous command the shell executed, and since that was "echo", > and that succeeded, the exit code is 0. This prevents a build failure > from being noticed automatically if a build dependency is lacking. > > Also, the error message in autogen.sh is now printed to to stderr, > not stdout > --- > autogen.sh | 6 +++--- > 1 files changed, 3 insertions(+), 3 deletions(-) > > diff --git a/autogen.sh b/autogen.sh > index c7bb679..f31013c 100755 > --- a/autogen.sh > +++ b/autogen.sh > @@ -5,9 +5,9 @@ if (libtoolize --version)< /dev/null> /dev/null 2>&1; then > LIBTOOLIZE=libtoolize > elif (glibtoolize --version)< /dev/null> /dev/null 2>&1; then > LIBTOOLIZE=glibtoolize > -else > - echo "libtoolize or glibtoolize was not found! Please install libtool." > - exit > + else > + echo "libtoolize or glibtoolize was not found! Please install libtool." > 1>&2 > + exit 1 > fi > > $LIBTOOLIZE --copy --force || exit 1 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libusbx-devel
