This is an automated email from Gerrit. Andreas Fritiofson ([email protected]) just uploaded a new patch set to Gerrit, which you can find at http://openocd.zylin.com/1534
-- gerrit commit 57a69b4c61228e614df550074a1050e1af1eb767 Author: Andreas Fritiofson <[email protected]> Date: Thu Aug 1 19:07:09 2013 +0200 configure: Add ARM libusb-1.0 header bug workaround Force the libusb-1.0 include dir to be treated as a system include path which suppresses the cast-align warnings otherwise failing the build. Change-Id: I738cfd793052b8772731d2feeef968ee893bd4bd Signed-off-by: Andreas Fritiofson <[email protected]> diff --git a/configure.ac b/configure.ac index 1f29013..93c125e 100644 --- a/configure.ac +++ b/configure.ac @@ -1073,6 +1073,11 @@ PKG_CHECK_MODULES([LIBUSB1], [libusb-1.0], [ PKG_CHECK_EXISTS([libusb-1.0 >= 1.0.9], [AC_DEFINE([HAVE_LIBUSB_ERROR_NAME], [1], [Define if your libusb has libusb_error_name()])], [AC_MSG_WARN([libusb-1.x older than 1.0.9 detected, consider updating])]) + AS_CASE([${host_cpu}], + [arm*], [ + LIBUSB1_CFLAGS=`echo $LIBUSB1_CFLAGS | sed 's/-I/-isystem /'` + AC_MSG_NOTICE([libusb-1.0 ARM workaround: LIBUSB1_CFLAGS changed to "$LIBUSB1_CFLAGS"]) + ]) ], [ use_libusb1=no AC_MSG_WARN([libusb-1.x not found, trying legacy libusb-0.1 as a fallback; consider installing libusb-1.x instead]) -- ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
