Building ACRN hypervisor source code with scenario occurs compile fail


Geoffroy Van Cutsem
 

Very good – thanks for confirmation!

 

From: acrn-users@... <acrn-users@...> On Behalf Of Lana Qin(BJ-RD)
Sent: Wednesday, December 2, 2020 10:43 AM
To: acrn-users@...
Subject: Re: [acrn-users] Building ACRN hypervisor source code with scenario occurs compile fail

 

Hi Geoffroy,

 

After checking my tool script file, I found I missed libpciaccess-dev and libevent-dev these 2 libs.
After install them, ACRN Hypervisor is built and installed success.

Thank you!
Lana


Lana Qin(BJ-RD)
 

Hi Geoffroy,


After checking my tool script file, I found I missed libpciaccess-dev and libevent-dev these 2 libs.
After install them, ACRN Hypervisor is built and installed success.

Thank you!
Lana


Geoffroy Van Cutsem
 

Hi Lana,

 

You are missing build dependencies on your machine (at least libevent-dev and libpciaccess-dev from what I can see below). Can you make sure you have all build dependencies correctly installed on your dev machine – see https://projectacrn.github.io/latest/getting-started/building-from-source.html#install-build-tools-and-dependencies for details.

 

Let us know if you’re not using Debian/Ubuntu as the package names and installation method will be slightly different then.

 

Geoffroy

 

From: acrn-users@... <acrn-users@...> On Behalf Of Liu, Fuzhong
Sent: Wednesday, December 2, 2020 9:20 AM
To: acrn-users@...
Subject: Re: [acrn-users] Building ACRN hypervisor source code with scenario occurs compile fail

 

Hi Lana

I can’t reproduce this issue on my Ubuntu 18.04:

Do you use Ubuntu 18.04?

If not, please share the info about your build environment.

 

make all BOARD=nuc7i7dnb SCENARIO=industry RELEASE=0

 

 

 

Thanks!

 

BR.

Fuzhong

From: acrn-users@... <acrn-users@...> On Behalf Of Lana Qin(BJ-RD)
Sent: Wednesday, December 2, 2020 1:51 PM
To: acrn-users@...
Subject: [acrn-users] Building ACRN hypervisor source code with scenario occurs compile fail

 

Hi ACRN Developer,

 

       I need help for ACRN hypervisor source code with scenario occur compile fail issue. The error occurs by using nuc7i7dnb BOARD and industry SCENARIO based on acrn-hypervisor-2.2 source code, the code is download from

https://github.com/projectacrn/acrn-hypervisor/releases/tag/v2.2,

 

  1. RELEASE=0

make all BOARD=nuc7i7dnb SCENARIO=industry RELEASE=0

 

error log:

server.c:35:10: fatal error: event2/event.h: No such file or directory

#include <event2/event.h>

          ^~~~~~~~~~~~~~~~

compilation terminated.

Makefile:38: recipe for target '/home/acrn/work/acrn-hypervisor/build/misc/tools/acrn-crashlog/usercrash/obj/server.o' failed

 

  1. RELEASE=1

make all BOARD=nuc7i7dnb SCENARIO=industry RELEASE=1

 

Error log:

hw/pci/gsi_sharing.c:13:10: fatal error: pciaccess.h: No such file or directory

#include <pciaccess.h>

          ^~~~~~~~~~~~~

compilation terminated.

 

BRs,

Lana

 

 

 

保密声明:

本邮件含有保密或专有信息,仅供指定收件人使用。严禁对本邮件或其内容做任何未经授权的查阅、使用、复制或转发。

CONFIDENTIAL NOTE:

This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or forwarding of this email or the content of this email is strictly prohibited.


Liu, Fuzhong
 

Hi Lana

I can’t reproduce this issue on my Ubuntu 18.04:

Do you use Ubuntu 18.04?

If not, please share the info about your build environment.

 

make all BOARD=nuc7i7dnb SCENARIO=industry RELEASE=0

 

 

 

Thanks!

 

BR.

Fuzhong

From: acrn-users@... <acrn-users@...> On Behalf Of Lana Qin(BJ-RD)
Sent: Wednesday, December 2, 2020 1:51 PM
To: acrn-users@...
Subject: [acrn-users] Building ACRN hypervisor source code with scenario occurs compile fail

 

Hi ACRN Developer,

 

       I need help for ACRN hypervisor source code with scenario occur compile fail issue. The error occurs by using nuc7i7dnb BOARD and industry SCENARIO based on acrn-hypervisor-2.2 source code, the code is download from

https://github.com/projectacrn/acrn-hypervisor/releases/tag/v2.2,

 

  1. RELEASE=0

make all BOARD=nuc7i7dnb SCENARIO=industry RELEASE=0

 

error log:

server.c:35:10: fatal error: event2/event.h: No such file or directory

#include <event2/event.h>

          ^~~~~~~~~~~~~~~~

compilation terminated.

Makefile:38: recipe for target '/home/acrn/work/acrn-hypervisor/build/misc/tools/acrn-crashlog/usercrash/obj/server.o' failed

 

  1. RELEASE=1

make all BOARD=nuc7i7dnb SCENARIO=industry RELEASE=1

 

Error log:

hw/pci/gsi_sharing.c:13:10: fatal error: pciaccess.h: No such file or directory

#include <pciaccess.h>

          ^~~~~~~~~~~~~

compilation terminated.

 

BRs,

Lana

 

 

 

保密声明:

本邮件含有保密或专有信息,仅供指定收件人使用。严禁对本邮件或其内容做任何未经授权的查阅、使用、复制或转发。

CONFIDENTIAL NOTE:

This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or forwarding of this email or the content of this email is strictly prohibited.


Lana Qin(BJ-RD)
 

Hi ACRN Developer,

 

       I need help for ACRN hypervisor source code with scenario occur compile fail issue. The error occurs by using nuc7i7dnb BOARD and industry SCENARIO based on acrn-hypervisor-2.2 source code, the code is download from

https://github.com/projectacrn/acrn-hypervisor/releases/tag/v2.2,

 

1)      RELEASE=0

make all BOARD=nuc7i7dnb SCENARIO=industry RELEASE=0

 

error log:

server.c:35:10: fatal error: event2/event.h: No such file or directory

#include <event2/event.h>

          ^~~~~~~~~~~~~~~~

compilation terminated.

Makefile:38: recipe for target '/home/acrn/work/acrn-hypervisor/build/misc/tools/acrn-crashlog/usercrash/obj/server.o' failed

 

2)      RELEASE=1

make all BOARD=nuc7i7dnb SCENARIO=industry RELEASE=1

 

Error log:

hw/pci/gsi_sharing.c:13:10: fatal error: pciaccess.h: No such file or directory

#include <pciaccess.h>

          ^~~~~~~~~~~~~

compilation terminated.

 

BRs,

Lana

 

 



保密声明:
本邮件含有保密或专有信息,仅供指定收件人使用。严禁对本邮件或其内容做任何未经授权的查阅、使用、复制或转发。
CONFIDENTIAL NOTE:
This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or forwarding of this email or the content of this email is strictly prohibited.