From: "Rebecca Cran" <rebecca@bluestop.org>
To: devel@edk2.groups.io
Subject: Building EDK2 code on arm64 (aarch64) - BaseTools fails
Date: Tue, 9 Apr 2019 22:57:35 -0600 [thread overview]
Message-ID: <e4699c53-7253-05b3-f188-eacce244f8e6@bluestop.org> (raw)
Is there any expectation that EDK2 will build on non-x86 systems?
I tried building BaseTools (from git master,
ae2fb9ead47b5abaf2a4e815b5f57c8f4838b221) using GCC 8.2 on a SoftIron
OverDrive 1000 (running FreeBSD) but there are lots of errors, such as:
gcc -c -I .. -I ../Include/Common -I ../Include/ -I
../Include/IndustryStandard -I ../Common/ -I .. -I . -I ../Include/Arm/
-MD -fshort-wchar -fno-strict-aliasing -Wall -Werror
-Wno-deprecated-declarations -Wno-stringop-truncation -Wno-restrict
-Wno-unused-result -nostdlib -g -O2 BasePeCoff.c -o BasePeCoff.o
BasePeCoff.c: In function 'PeCoffLoaderGetPeHeader':
BasePeCoff.c:120:49: error: cast from pointer to integer of different
size [-Werror=pointer-to-int-cast]
*PeHdr = (EFI_IMAGE_OPTIONAL_HEADER_UNION *)
((UINTN)ImageContext->Handle + ImageContext->PeCoffHeaderOffset);
^
BasePeCoff.c:120:12: error: cast to pointer from integer of different
size [-Werror=int-to-pointer-cast]
*PeHdr = (EFI_IMAGE_OPTIONAL_HEADER_UNION *)
((UINTN)ImageContext->Handle + ImageContext->PeCoffHeaderOffset);
^
BasePeCoff.c: In function 'PeCoffLoaderImageAddress':
BasePeCoff.c:551:10: error: cast to pointer from integer of different
size [-Werror=int-to-pointer-cast]
return (UINT8 *) ((UINTN) ImageContext->ImageAddress + Address);
^
--
Rebecca Cran
next reply other threads:[~2019-04-10 4:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 4:57 Rebecca Cran [this message]
2019-04-10 14:41 ` [edk2-devel] Building EDK2 code on arm64 (aarch64) - BaseTools fails Philippe Mathieu-Daudé
2019-04-10 15:04 ` Rebecca Cran
2019-04-10 17:31 ` Laszlo Ersek
2019-04-11 0:09 ` Liming Gao
2019-04-11 2:07 ` Rebecca Cran
[not found] ` <159449609038BC58.19288@groups.io>
2019-04-11 3:21 ` Rebecca Cran
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e4699c53-7253-05b3-f188-eacce244f8e6@bluestop.org \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox