public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, adriano_fk@hotmail.com
Subject: Re: [edk2-devel] [edk2-test] Can't build edk2-test on x64 linux
Date: Thu, 28 Jan 2021 20:35:45 +0100	[thread overview]
Message-ID: <1c7336f5-f4ff-0f4e-4343-fb0418339d05@redhat.com> (raw)
In-Reply-To: <nQAu.1611861016617820112.i7uZ@groups.io>

On 01/28/21 20:10, Adriano Kultzak wrote:
> Hello.
> 
> I've been trying to build UEFI-SCT following these instructions https://github.com/tianocore/edk2-test/blob/master/uefi-sct/HowToBuild/How%20to%20build%20SCT%20in%20UDK2017.txt on linux Debian 10, using the latest edk2 available, also tried to build over vudk2017 https://github.com/tianocore/edk2/releases/tag/vUDK2017 , but it stops in this kind of error:
> ___________________________________________________________________________________________________________________________
> /home/repos/TestToolls/SctWorkspace2/SctPkg/TestCase/RIVL/Protocol/InternetProtocol4/Ip4/Ip4ENTSTest.c: In function ‘Ip4ENTSTestMain’:
> /home/repos/TestToolls/SctWorkspace2/SctPkg/TestCase/RIVL/Protocol/InternetProtocol4/Ip4/Ip4ENTSTest.c:119:23: warning: assignment to ‘EFI_IMAGE_UNLOAD’ from incompatible pointer type ‘EFI_STATUS (*)(void *)’ {aka ‘long long unsigned int (*)(void *)’} [-Wincompatible-pointer-types]
> LoadedImage->Unload = Ip4ENTSTestUnload;
> ^
> make: *** [GNUmakefile:337: /home/repos/TestToolls/SctWorkspace2/Build/UefiSct/DEBUG_GCC5/X64/SctPkg/TestCase/RIVL/Protocol/InternetProtocol4/Ip4/Ip4ENTSTest/OUTPUT/Ip4ENTSTest.obj] Error 1
> Could not build the UEFI SCT package
> ___________________________________________________________________________________________________________________________
> 
> Is there any currently known impediment to build UEFI-SCT in the linux environment or some other important details I'm missing? I appreciate any help.

Agreed -- the SCT build method is both untested with GCC and
significantly out of date esp. with regard to the multiple workspace
feature (PACKAGES_PATH, to be specific). I tried building SCT myself a
few weeks ago; it was very under-documented, and what I managed to
understand anyway indicated it had no support for PACKAGES_PATH.

Some of the edk2 platforms too are clearly never built with GCC.

Thanks
Laszlo


      reply	other threads:[~2021-01-28 19:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28 19:10 [edk2-test] Can't build edk2-test on x64 linux Adriano Kultzak
2021-01-28 19:35 ` Laszlo Ersek [this message]

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=1c7336f5-f4ff-0f4e-4343-fb0418339d05@redhat.com \
    --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