On Friday, April 17, 2015 03:18:54 PM Uwe Hermann wrote: > Hi, Hi > > Getting around "Warning: AX_CXX_COMPILE_STDCXX_11 macro is too old" was a > > bit of a pain. > > You need the latest autoconf-archive as per README, or you can manually > get that file as per the FAQ that autogen.sh should have printed. > I did see the link, and I do appreciate having the documentation so blatantly available. On the other hand, any manual step does become an issue when trying to automate the process.
> Note that this is only required for git users, it will not be an issue > for tarball users (no need for autoconf-archive etc). > Real men build from git. :p > > Python2.7 was picked up instead of python3. Easy fix, but an extra manual > > step, and it would be nice if it tried to pick up python3 by default. > > The libsigrok Python bindings can be used with both, Python 2.x and > Python 3.x, they work fine with either version (as per README). Which of > those is the default probably doesn't matter much (you can also enforce > either of them at ./configure-time as a user), but I personally wouldn't > mind making Python 3 the default. > Well, it does pick whichever python version is in /bin/python. Martin was saying in a reply to your mail that this seems reasonable. It may be so when building for one machine, but that becomes an issue when automating the build in some infrastructure which is not your machine. > > There was no check for python-numpy. I only found out I needed numpy when > > the build failed. > > Yup, no check currently (it's mentioned in the README as requirement > though). This is bug #533, patches for a portable proper check are welcome. > > http://sigrok.org/bugzilla/show_bug.cgi?id=533 > Ooh. I should have checked the bug tracker. > > Setuptools was not detected. I had to manually had configure.ac to make it > > > > ignore the check. It compiled fine after that; (not a patch): > > - BINDINGS_PYTHON="no"; python_msg="Python setuptools module > > required"> > > + BINDINGS_PYTHON="yes"; python_msg="Python setuptools module > > required" > That's strange, if you have setuptools for your respective Python > version (2 or 3) that should usually be picked up correctly. Feel free > to file a bug if this is reproducible for your setup, despite the correct > package being installed. > I will try to find a reproducible way of doing it. I did hit this on both machines where I tried it. Alex ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
