From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124])
 by mx.groups.io with SMTP id smtpd.web08.1076.1611862552648047935
 for <devel@edk2.groups.io>;
 Thu, 28 Jan 2021 11:35:52 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=a09jvZwy;
 spf=pass (domain: redhat.com, ip: 63.128.21.124, mailfrom: lersek@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1611862551;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=P8CyjYPI2WDC/EP9pzYz97smdv8Eqymaj16MhmUTDKw=;
	b=a09jvZwysBawlKh2c4emBSvqWMvCqg7+tSgALS1OdCBGtrFblquDoi4/VeR1NXfdVUCMyP
	h345F9FjOCLO+ChG+dstclbuPlS5/sFYVEDPNB6Vt8k/aPsDxsdyh6i3z2H+g4tbAqnpzV
	55cq8XijRdw1dJffL8Znh7rjvA9AVe4=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id
 us-mta-444-YzQNeiD7MeWlS77nXnQJLA-1; Thu, 28 Jan 2021 14:35:47 -0500
X-MC-Unique: YzQNeiD7MeWlS77nXnQJLA-1
Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx01.redhat.com (Postfix) with ESMTPS id E388A107ACE3;
	Thu, 28 Jan 2021 19:35:46 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-112-28.ams2.redhat.com [10.36.112.28])
	by smtp.corp.redhat.com (Postfix) with ESMTP id 44E395C1B4;
	Thu, 28 Jan 2021 19:35:46 +0000 (UTC)
Subject: Re: [edk2-devel] [edk2-test] Can't build edk2-test on x64 linux
To: devel@edk2.groups.io, adriano_fk@hotmail.com
References: <nQAu.1611861016617820112.i7uZ@groups.io>
From: "Laszlo Ersek" <lersek@redhat.com>
Message-ID: <1c7336f5-f4ff-0f4e-4343-fb0418339d05@redhat.com>
Date: Thu, 28 Jan 2021 20:35:45 +0100
MIME-Version: 1.0
In-Reply-To: <nQAu.1611861016617820112.i7uZ@groups.io>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16
Authentication-Results: relay.mimecast.com;
	auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=lersek@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit

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