Re: Symbol lookup errors while building C++ source code

2017-04-23 Thread Rick Payne (Offshore)
> What I think is a better approach is to take separatey the OSv kernel with > just cpiod.so and mkfs.so (i.e., take build/release/loader.img) and the > files, and compose the image with the size you want and uploading the files > you want to it. This is more-or-less what the Mikelangelo

Re: Symbol lookup errors while building C++ source code

2017-04-23 Thread Rick Payne (Offshore)
> On 23 Apr 2017, at 05:14, Nadav Har'El wrote: > > Pekka, another question we should ask ourselves is what is the plan with > Capstan, and more importantly, the binary OSv releases. The OSv v0.24 version > he used is two years old (!). If we're not going to produce any

Re: Symbol lookup errors while building C++ source code

2017-04-23 Thread Nadav Har'El
On Sun, Apr 23, 2017 at 2:06 PM, Avi Kivity wrote: > It could be the new ABI, see https://gcc.gnu.org/ > onlinedocs/libstdc++/manual/using_dual_abi.html. > > > Try compiling your code with _GLIBCXX_USE_CXX11_ABI=0. > Indeed. Check out also commit

Re: Symbol lookup errors while building C++ source code

2017-04-23 Thread Avi Kivity
It could be the new ABI, see https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html. Try compiling your code with _GLIBCXX_USE_CXX11_ABI=0. On 04/23/2017 01:41 PM, Niels Bergsma wrote: Hi all, I've been trying to build simple C++ apps for the past few weeks on OSV. I

Symbol lookup errors while building C++ source code

2017-04-23 Thread Niels Bergsma
Hi all, I've been trying to build simple C++ apps for the past few weeks on OSV. I frequently receive "failed looking up symbol" errors and I can't figure out how to solve them properly. Simple programs like HelloWorld or variants which include simple shared library work correctly, but more