The boost detection mechanism assumes that if a CROSS_PREFIX is
specified the library has to be installed in
"build/downloaded_packages/aarch64/boost/install" folder in the OSv
sources folder.
This is not the case when cross compiling on a distro that supports
multiarch and the boost libraries are
When cross compiling, it would be good to support the following two
cases -
* Distro provided cross compiler + libraries - This is the case when a
distro with multi-arch support (e.g., Debian derivaties)
* Local libraries installation - Needed when the distro doesn't
support multi-arch or the
Hi,
Here's a couple of fixes to rely on the compiler to resolve library
locations during the build rather than using hard coded paths in the
build/Makefile when cross compiling. With these, I am able to cross
build OSv for arm64 on Debian using -
$ export CROSS_PREFIX="aarch64-linux-gnu-"
Hi,
On Thu, Feb 11, 2021 at 9:06 AM Nadav Har'El wrote:
> On Thu, Feb 11, 2021 at 7:42 AM Waldek Kozaczuk
> wrote:
>
>>
>> #1 0x10037954 in test_bsd_tcp1::tcp_server (this=0x206ff988)
>> at /home/wkozaczuk/projects/osv/tests/tst-bsd-tcp1-zsnd.cc:114
>>
>> 114 int bytes2
Hello everyone,
I would like to step into this topic, maybe my experience may help and also
you may help me too. A couple of months ago, I figured that I can't debug
Toro KVM guests by using the QEMU built-in gdbstub. I tried hwbreak but
that did not work either. The execution was not stopping on