Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

Am 17.01.2017 um 22:39 schrieb Ryan Gonzalez: Whoops, missed that one! Change line 715 to: std::cerr << "Warning: " << msg.str() << '\n'; Success! With these 2 fixes, it now builds using clang (with GNU libstdc++): -- Set runtime path of "/home/oberstet/pypy-5.6-linux_x86_64-portable/sit

Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

Hi Ryan, Am 17.01.2017 um 20:56 schrieb Ryan Gonzalez: This one looks like a bug in cppyy! Try going to clingcwrapper.cxx and changing line 525 from: Yeah, that helps: the issue at line 525 is gone, but the 2nd issue at line 715 persists: /tmp/pip-BVnCrW-build/src/backend/cppyy/src/clingcw

Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

Hi Wim, Am 17.01.2017 um 20:01 schrieb wlavrij...@lbl.gov: Hi Tobias, 1. gcc 5 / libstdc++ 2. gcc 4.9 / libstdc++ 3. clang / libc++ 4. clang / libstdc++ 1/3/4 fails building cppy. how does 3 fail? I presume differently than 1, 4? https://gist.github.com/oberstet/1771d9142cf566c5a877de0df5

Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

Hi Wim, I'm saying to _remove_ the `-stdlib=libc++` that's currently there. Yes and I expect it to work. But I wrote the pip, and ideally, I get that fixed to allow what Tobias is doing. B/c if the '-stdlib=libc++' is removed, the build system will not pick it up either (it's off by default).

Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

Hi Ryan, with CXX=clang++ the build nearly finishes (I am a moron, sorry, clang isn't that clever), that is CC=`which clang` \ CXX=`which clang++` \ CXXFLAGS="-std=c++11" \ MAKE_NPROCS=4 \ ~/pypy-5.6-linux_x86_64-portable/bin/pip install --no-cache-dir --verbos

Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

Hi Antonio, Note: for now I am fine, I managed to build it using gcc 4.9 toolchain. Need to see how far I get with captnproto now .. ​if you are interested in capnproto, you might want to try capnpy: it's written in pure python and it has been designed to be super fast on pypy (and it's very

Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

Am 17.01.2017 um 19:03 schrieb Ryan Gonzalez: What happens if you remove the `-stdlib=libc++`? Seems like that's where the Clang build error is coming from. 1) removing explicit stdlib selection leads to the following linker error https://gist.github.com/oberstet/f75b9618b12b1e61289b147fcfd90b

[pypy-dev] os_read & rposix.c_read

Hi all, Anyone knows why pypy.module._file.readinto uses a locally defined ‘os_read’ rather than rpython.rlib.rposix.c_read? It seems that the functions are defined almost the same way, except one uses rffi.CCHARP the other uses rffi.VOIDP, and the rposix.c_read has a more complete ExternalCompi

Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

Hi Ryan, Tobias, On Tuesday 2017-01-17 21:39, Ryan Gonzalez wrote: Whoops, missed that one! Change line 715 to: std::cerr << "Warning: " << msg.str() << '\n'; indeed, thanks! Now fixed in the repository. Hopefully up soon in the pip (takes more testing, hence time) ... Best regards,

Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

Whoops, missed that one! Change line 715 to: std::cerr << "Warning: " << msg.str() << '\n'; \-- Ryan (ライアン) Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else On Jan 17 2017, at 3:30 pm, Tobias Oberstein wrote: > Hi Ryan, > >

Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

This one looks like a bug in cppyy! Try going to clingcwrapper.cxx and changing line 525 from: cppresult->std::string::~string(); to: cppresult->std::string::~basic_string(); (e.g. change `~string` to `~basic_string`). \-- Ryan (ライアン) Yoko Shimomur

Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

Hi Tobias, https://gist.github.com/oberstet/d260ee15c81954bea8298b7400d04870 those symbols (ZN4ROOT17TGenericClassInfoD1Ev and friends) live in libCore.so which is installed under site packages and you can link with that. However, the backend should add all those symbols and make them availabl

Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

​Hi,​ On Tue, Jan 17, 2017 at 5:51 PM, Tobias Oberstein < tobias.oberst...@gmail.com> wrote: > Note: for now I am fine, I managed to build it using gcc 4.9 toolchain. > Need to see how far I get with captnproto now .. > ​if you are interested in capnproto, you might want to try capnpy: it's writ

Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

In your Makefile, change this: CXX=`which clang` \ to: CXX=`which clang++` \ -- Ryan (ライアン) Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else http://kirbyfan64.github.io/ On Jan 17, 2017 12:41 PM, "Tobias Oberstein" wrote: > Am 17.01.2017 um 19:03 schrieb Ryan Gonzal

Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

Hi Tobias, 1. gcc 5 / libstdc++ 2. gcc 4.9 / libstdc++ 3. clang / libc++ 4. clang / libstdc++ 1/3/4 fails building cppy. how does 3 fail? I presume differently than 1, 4? 2 builds cppyy, but the example bails out. In which way? What toolchain/system are you using? Gentoo, SuSE and Mac

Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

On Jan 17, 2017 12:37 PM, wrote: Hi Ryan, On Tuesday 2017-01-17 18:28, Ryan Gonzalez wrote: > I think you misunderstood me. Your build log shows: > no, I didn't. :) It's not my build log, it's Tobias's. *facepalm* I need to double-check who exactly I'm replying to... :/ I'm saying to _re

Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

Hi Ryan, On Tuesday 2017-01-17 18:28, Ryan Gonzalez wrote: I think you misunderstood me. Your build log shows: no, I didn't. :) It's not my build log, it's Tobias's. I'm saying to _remove_ the `-stdlib=libc++` that's currently there. Yes and I expect it to work. But I wrote the pip, and i

Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

I think you misunderstood me. Your build log shows: oberstet@thinkpad-t430s:~/scm/oberstet/scratchbox/cpp/capnproto/test1$ make cpppypy CC=`which clang` \ CXX=`which clang` \ CXXFLAGS="-std=c++11 -stdlib=libc++" \ LDFLAGS="-stdlib=libc++" \ MAKE_NPROCS=4 \ ~/pypy-5.6-linux_x86_64-

Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

Hi, On Tuesday 2017-01-17 18:03, Ryan Gonzalez wrote: What happens if you remove the `-stdlib=libc++`? Seems like that's where the Clang build error is coming from. that will likely be a solution, b/c that wrapper file is put in place if the libcxx from clang is not used. Seems a configuration

Re: [pypy-dev] cppyy fails to build on gcc 5 and clang

What happens if you remove the `-stdlib=libc++`? Seems like that's where the Clang build error is coming from. \-- Ryan (ライアン) Yoko Shimomura > ryo (supercell/EGOIST) > Hiroyuki Sawano >> everyone else On Jan 17 2017, at 11:53 am, Tobias Oberstein wrote: > Hi

[pypy-dev] cppyy fails to build on gcc 5 and clang

Hi guys, please see (reposting here to grab attention as hinted by Armin) https://bitbucket.org/pypy/pypy/issues/2467/cppyy-fails-to-build-on-gcc-5-and-clang Note: for now I am fine, I managed to build it using gcc 4.9 toolchain. Need to see how far I get with captnproto now .. Cheers, /Tobi

Re: [pypy-dev] Leysin sprint?

Hi, I'd prefer the classic Leysin sprint :). I will probably be unavailable the first two weeks of March; other than that, any week should be fine for me. On Mon, Jan 16, 2017 at 8:59 PM, Maciej Fijalkowski wrote: > I have a place to stay in Zurich so it's a bit of a win for me :-) > > I would p