From: Arpan Mukherjee <arpanbzs@gmail.com>
To: devel@edk2.groups.io
Subject: [edk2-test]
Date: Thu, 29 Oct 2020 10:59:36 +0530 [thread overview]
Message-ID: <CADLBfVDrD5+WRw-1Lx1x10pML9o7vdh_O0j6bopqWJL8K8G+mQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3005 bytes --]
Not able to build SctPkg using UDK2017 for X64 architecture in
Linux(ubuntu). In SctPkg/build.sh. Showing COMPONENT_TYPE not given. Here
is the log.
. SctPkg/build.sh X64 GCC
Target: X64
Build: other
Unsupported target architecture 'X64'!
TOOLCHAIN is GCC49
Toolchain prefix: GCC49_X64_PREFIX=
Building from: /home/xilinx/arpanm/edk2-vUDK2017
using prebuilt tools
Building GenBin
make: Entering directory
'/home/xilinx/arpanm/edk2-vUDK2017/SctPkg/Tools/Source/GenBin'
Attempting to detect ARCH from 'uname -m': x86_64
Detected ARCH of X64 using uname.
make: Warning: File
'/home/xilinx/arpanm/edk2-vUDK2017/BaseTools/Source/C/Makefiles/footer.makefile'
has modification time 40845275 s in the future
gcc -c -MD -fshort-wchar -fno-strict-aliasing -Wall -Werror
-Wno-deprecated-declarations -Wno-unused-result -nostdlib -c -g -I
/home/xilinx/arpanm/edk2-vUDK2017/BaseTools/Source/C -I
/home/xilinx/arpanm/edk2-vUDK2017/BaseTools/Source/C/Include/Common -I
/home/xilinx/arpanm/edk2-vUDK2017/BaseTools/Source/C/Include/ -I
/home/xilinx/arpanm/edk2-vUDK2017/BaseTools/Source/C/Include/IndustryStandard
-I /home/xilinx/arpanm/edk2-vUDK2017/BaseTools/Source/C/Common/ -I .. -I .
-I /home/xilinx/arpanm/edk2-vUDK2017/BaseTools/Source/C/Include/X64/ -O2
GenBin.c -o GenBin.o
gcc -o /home/xilinx/arpanm/edk2-vUDK2017/BaseTools/Source/C/bin/GenBin
GenBin.o -L/home/xilinx/arpanm/edk2-vUDK2017/BaseTools/Source/C/libs
make: warning: Clock skew detected. Your build may be incomplete.
make: Leaving directory
'/home/xilinx/arpanm/edk2-vUDK2017/SctPkg/Tools/Source/GenBin'
Build environment: Linux-4.15.0-99-generic-x86_64-with-Ubuntu-16.04-xenial
Build start time: 20:01:29, Feb.26 2016
WORKSPACE = /home/xilinx/arpanm/edk2-vUDK2017
ECP_SOURCE = /home/xilinx/arpanm/edk2-vUDK2017/EdkCompatibilityPkg
EDK_SOURCE = /home/xilinx/arpanm/edk2-vUDK2017/EdkCompatibilityPkg
EFI_SOURCE = /home/xilinx/arpanm/edk2-vUDK2017
EDK_TOOLS_PATH = /home/xilinx/arpanm/edk2-vUDK2017/BaseTools
CONF_PATH = /home/xilinx/arpanm/edk2-vUDK2017/Conf
Architecture(s) = X64
Build target = DEBUG
Toolchain = GCC49
Active Platform =
/home/xilinx/arpanm/edk2-vUDK2017/SctPkg/UEFI/UEFI_SCT.dsc
Processing meta-data ..
build.py...
/home/xilinx/arpanm/edk2-vUDK2017/SctPkg/TestCase/UEFI/EFI/BootServices/ImageServices/BlackBoxTest/Dependency/InvalidImage1/InvalidImage1.inf(...):
error 5000: COMPONENT_TYPE is not given
- Failed -
Build end time: 20:01:32, Feb.26 2016
Build total time: 00:00:03
Could not build the UEFI SCT package
Please help in resolving the issue.
Thanks and regards
Arpan Mukherjee
5th-year Dual Degree student
Instrumentation and Signal Processing
Dept. of Electrical Engineering
IIT Kharagpur
[image: Mailtrack]
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&>
Sender
notified by
Mailtrack
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&>
10/29/20,
10:59:21 AM
[-- Attachment #2: Type: text/html, Size: 4811 bytes --]
reply other threads:[~2020-10-29 5:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CADLBfVDrD5+WRw-1Lx1x10pML9o7vdh_O0j6bopqWJL8K8G+mQ@mail.gmail.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