Hi, On Sun, May 01, 2016 at 05:53:59PM +0100, José Silva wrote: > I'm trying to build the last version of libsigrok for support to Hantek > 6022BL oscilloscope. I'm running Manjaro and the error shows up either
I've been looking into 6022BL support btw., this shouldn't be too hard to add. The main difference to 6022BE as far as I've analyzed this is: 6022BE has CTL2 tied to IFCLK, whereas 6022BL has CTL0 tied to IFCLK. I changed fx2lafw to accommodate for this for a quick test, and while it looked like it might work there was a strange high-pitch noise coming from the device after doing so, thus I turned off power quickly, just in case. This might need some more investigation and potentially additional changes, but it doesn't look like there'll be much code needed to support the 6022BL's scope part. There's no point IMHO to try to add their "native" LA support btw. Just using the button on the device will switch the VID/PID to something that works out of the box with fx2lafw and is *much* more usable than the "native" 6022BL LA support for that device. > using Pamac or building the git locally on the terminal. Pamac doesn't > show history from the beginning, the extracts here are from the local > build terminal which might not have the same config as the Manjaro > repository. Anyway, the errors are the same. > > GEN bindings/ruby/doc.i > GEN bindings/ruby/classes_wrap.cpp > CXX bindings/ruby/classes_wrap.o > In file included from /usr/include/c++/5.3.0/type_traits:35:0, > from /usr/include/sigc++-2.0/sigc++/visit_each.h:22, > from /usr/include/sigc++-2.0/sigc++/functors/slot.h:6, > from /usr/include/sigc++-2.0/sigc++/signal_base.h:27, > from /usr/include/sigc++-2.0/sigc++/signal.h:8, > from /usr/include/sigc++-2.0/sigc++/sigc++.h:104, > from /usr/include/glibmm-2.4/glibmm/thread.h:50, > from /usr/include/glibmm-2.4/glibmm.h:89, > from bindings/ruby/classes_wrap.cpp:2011: > /usr/include/c++/5.3.0/bits/c++0x_warning.h:32:2: error: #error This > file requires compiler and library support for the ISO C++ 2011 > standard. This support must be enabled with the -std=c++11 or > -std=gnu++11 compiler options. > #error This file requires compiler and library support \ > ^ > In file included from /usr/include/glibmm-2.4/glibmm/exception.h:25:0, > from /usr/include/glibmm-2.4/glibmm/error.h:23, > from /usr/include/glibmm-2.4/glibmm/thread.h:48, > from /usr/include/glibmm-2.4/glibmm.h:89, > from bindings/ruby/classes_wrap.cpp:2011: > /usr/include/glibmm-2.4/glibmm/ustring.h:102:9: error: expected > nested-name-specifier before ‘iterator_category’ > using iterator_category = std::bidirectional_iterator_tag; > > This is followed by an immense series of errors which I presume to be a > consequence of the first. The compiler supports c++11 and the flag is > activated. Hm, looks strange indeed. Can you file a bug at sigrok.org/bugzilla please, so we'll keep track of this? Also, try --disable-ruby and see if that is a usable workaround for the time being (unless you want to use the Ruby bindings, of course). Uwe. -- http://hermann-uwe.de | http://randomprojects.org | http://sigrok.org ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel