Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add UP2 ACRN SBL binary to E2E build #2344

Closed
mwang106 opened this issue Jan 15, 2019 · 2 comments
Closed

Add UP2 ACRN SBL binary to E2E build #2344

mwang106 opened this issue Jan 15, 2019 · 2 comments

Comments

@mwang106
Copy link
Contributor

Integrate acrn sbl binary for up2 to E2E build

@mwang106 mwang106 assigned ghost Jan 15, 2019
@mwang106
Copy link
Contributor Author

[External_System_ID] ACRN-2511

@mwang106 mwang106 added area: hypervisor type: feature New feature status: open The issue is working in progress priority: high labels Jan 15, 2019
wenlingz pushed a commit that referenced this issue Jan 18, 2019
Currently, we support SBL on two different boards.
So build and install them all in E2E build.

Tracked-On: #2344
Signed-off-by: Tw <wei.tan@intel.com>
Reviewed-by: Binbin Wu <binbin.wu@intel.com>
ZideChen0 pushed a commit to ZideChen0/acrn-hypervisor that referenced this issue Jan 18, 2019
Currently, we support SBL on two different boards.
So build and install them all in E2E build.

Tracked-On: projectacrn#2344
Signed-off-by: Tw <wei.tan@intel.com>
Reviewed-by: Binbin Wu <binbin.wu@intel.com>
wenlingz pushed a commit that referenced this issue Jan 22, 2019
Add rules for installing debug information.

Tracked-On: #2344
Signed-off-by: Tw <wei.tan@intel.com>
Reviewed-by: Binbin Wu <binbin.wu@intel.com>
@Mingyuan18
Copy link

SBL UP2 SOS boot successfully with sos_boot.img. Build info:
SOS: 27230 acrn tag: acrn-2019w03.2.160000p

@Mingyuan18 Mingyuan18 added status: closed The issue been closed and removed status: open The issue is working in progress labels Jan 29, 2019
wenlingz pushed a commit that referenced this issue Feb 28, 2019
Currently, we are enforcing the _FORTIFY_SOURCE=2 without any
previous detection if the macro has been already defined, e.g.
by environment, or is just enabled by compiler by default on
some distributions (e.g. Gentoo).

This could result in the error like this:
<command-line>:0:0: error: "_FORTIFY_SOURCE" redefined [-Werror]
<built-in>: note: this is the location of the previous definition

Tracked-On: #2344
Signed-off-by: Tw <wei.tan@intel.com>
Reviewed-by: Binbin Wu <binbin.wu@intel.com>
Acked-by: Yin Fengwei <fengwei.yin@intel.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants