Hello, This issue seems the same as an other corrected by : https://github.com/libusb/libusb-compat-0.1/pull/10/commits/3db2078a86c5dbed3d7341cf1bc87290d6f63c58 Gwen
On Wed, 26 Apr 2017 18:23:48 +0200 Gerhard Sittig <gerhard.sit...@gmx.net> wrote: > On Wed, Apr 26, 2017 at 15:58 +0200, Rudolf Reuter wrote: > > > > Build sigrok under Mac OS Sierra 10.12.4, problems (2017-04-23) > > > > Problem #1, libsigrok: > > compile errors: > > In file included from librigrok/src/hardware/ftdi-la/api.c:21: > > In file included from /opt/local/include/ftdi.h:20: > > /opt/local/include/usb.h:81:2: error: unknown type name > > 'u_int8_t'; did you mean '__int8_t'? > > u_int8_t bLength; > > ^~~~~~~~ > > __int8_t > > ... > > 20 errors > > Comment: type u_int8_t is not defined > > What's the origin of that /opt/local/include/usb.h file? It > appears to be a "system header" and most probably is not a sigrok > provided one. Which suggests that the issue is caused by some > other upstream component, and cannot get fixed by the sigrok > project. > > BTW the uint8_t etc types are provided by <stdint.h> assuming > that your compiler supports C99 (or a preview of it). > > > > Problem #2, pulseview, compile error on warnings > > Comment to file pulseview/CMakeLists.txt: > > The option "Build without -Werror" FALSE > > must be changed to TRUE > > > > Solution: Edit file pulseview/CMakeLists.txt > > $ cat CMakeLists.txt | grep -nC 2 Werror > > 31-#--------------------------------------------------- > > 32-# 2017-04-23 RR > > 33:option(DISABLE_WERROR "Build without -Werror" TRUE) > > 34:#option(DISABLE_WERROR "Build without -Werror" FALSE) > > ... > > Hint: A "diff" more appropriately represents what actually has > changed. See the diff(1) and patch(1) commands. Train yourself > to run diff(1) with -u or -c for human readable output. Or just > use git(1) when you already got the sandbox on your machine. > > What exactly is the issue here? Can you expand? Is it a problem > when warnings are considered an error? Which are the warnings > that trouble you, and would it be more appropriate or helpful to > fix those warnings instead of just silencing the compiler? After > all the compiler tries to tell you something when it emits a > warning. :) > > > virtually yours > Gerhard Sittig > -- > If you don't understand or are scared by any of the above > ask your parents or an adult to help you. > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > sigrok-devel mailing list > sigrok-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sigrok-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
