From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from nwk-aaemail-lapp01.apple.com (nwk-aaemail-lapp01.apple.com [17.151.62.66]) by mx.groups.io with SMTP id smtpd.web12.25699.1602878737815544171 for ; Fri, 16 Oct 2020 13:05:37 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@apple.com header.s=20180706 header.b=JYdZO4zC; spf=pass (domain: apple.com, ip: 17.151.62.66, mailfrom: afish@apple.com) Received: from pps.filterd (nwk-aaemail-lapp01.apple.com [127.0.0.1]) by nwk-aaemail-lapp01.apple.com (8.16.0.43/8.16.0.42) with SMTP id 09GJsYUF063204; Fri, 16 Oct 2020 13:05:34 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : content-type : mime-version : subject : date : references : to : in-reply-to : message-id; s=20180706; bh=3kj6CH+K6iOFS5l8ir+62hoWpA7GGZ/F/vygEVr8/tQ=; b=JYdZO4zCVV+cpeRub/ZOxqbou1XdzUZx7+2uvmcPNk2Qun8s8wvp/AgEaeFfay4eC6tH BVn50byBP/Axv9cMuOhmSL62bkC8L7Crr8LG1+bULUrbVeGTLid6f1+AnbG1TQ9A5JgT vHO8D7Ac+44HM+BTXnB1VhR4IyEZz2TrmfavJFemkez8rUv8aK/3sonBisAQ/QzHSoQh OWwhUWFjPCGloVHZdJIvTESNzY8wAqwaf9X0y92j+ztBr8gusqDdugbRnPXAswbCFIZg dnZ9XHrvOyr8HUgcpa3xBojirpvD80V7c3W9Ngfllp3mJohX9168xMjLw/a/yEVaYQZ4 nA== Received: from rn-mailsvcp-mta-lapp02.rno.apple.com (rn-mailsvcp-mta-lapp02.rno.apple.com [10.225.203.150]) by nwk-aaemail-lapp01.apple.com with ESMTP id 344smx2648-14 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 16 Oct 2020 13:05:33 -0700 Received: from rn-mailsvcp-mmp-lapp03.rno.apple.com (rn-mailsvcp-mmp-lapp03.rno.apple.com [17.179.253.16]) by rn-mailsvcp-mta-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.6.20200729 64bit (built Jul 29 2020)) with ESMTPS id <0QIB000WG957TEM0@rn-mailsvcp-mta-lapp02.rno.apple.com>; Fri, 16 Oct 2020 13:05:31 -0700 (PDT) Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp03.rno.apple.com by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.6.20200729 64bit (built Jul 29 2020)) id <0QIB00V008WJ7I00@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Fri, 16 Oct 2020 13:05:31 -0700 (PDT) X-Va-A: X-Va-T-CD: 4aed6d51041d65cf37c631f6e73d9d3b X-Va-E-CD: 0e97c8df0489df178b983445b89867ca X-Va-R-CD: 8b007e8ffd3365a77500ff05637ced77 X-Va-CD: 0 X-Va-ID: adc70518-0c75-413d-98d3-ffa8787868a0 X-V-A: X-V-T-CD: 4aed6d51041d65cf37c631f6e73d9d3b X-V-E-CD: 0e97c8df0489df178b983445b89867ca X-V-R-CD: 8b007e8ffd3365a77500ff05637ced77 X-V-CD: 0 X-V-ID: 6221d662-9ee3-4b7b-837a-6f3a8a30dd04 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235,18.0.687 definitions=2020-10-16_10:2020-10-16,2020-10-16 signatures=0 Received: from [17.235.61.27] (unknown [17.235.61.27]) by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.6.20200729 64bit (built Jul 29 2020)) with ESMTPSA id <0QIB00HFU955RB00@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Fri, 16 Oct 2020 13:05:30 -0700 (PDT) From: "Andrew Fish" MIME-version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\)) Subject: Re: [edk2-devel] Issues with edk2 compilation with xcode5 on mac OS - files compiled but strange behaviors Date: Fri, 16 Oct 2020 13:05:29 -0700 References: <1D62256C-60B6-4453-AA33-1DCF7E125DD9@apple.com> To: edk2-devel-groups-io , Daniele Crudo In-reply-to: Message-id: X-Mailer: Apple Mail (2.3608.120.23.2.1) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235,18.0.687 definitions=2020-10-16_10:2020-10-16,2020-10-16 signatures=0 Content-type: multipart/alternative; boundary="Apple-Mail=_7D63F6C4-8ACF-4D40-A9E9-5C862514A607" --Apple-Mail=_7D63F6C4-8ACF-4D40-A9E9-5C862514A607 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Oct 16, 2020, at 12:24 PM, Daniele Crudo wr= ote: >=20 >=20 > Sorry I missed the edk2-devel in cc, resending. >=20 > OK so the DEBUG and RELEASE both build with -Os. This is firmware things= have to fit in the ROM. The big difference between DEBUG and release is th= e DEBUG prints get stripped out, so that usually means timing issues :(.=20 >=20 > The compiler flags live in BaseTools/Conf/tools_def.template and you ca= n edit them in Conf/tools_def.txt >=20 > ok, thanks for this, I was hoping in optimization issue but it seems it'= s not the case (?) >=20 > What logo are your talking about? I see the TianoCore logo failed in you= r macOS debug log as I would expect [1]d: > "HII Image Package with logo not found in PE/COFF resource section=E2=80= = =9D > I don=E2=80=99t see that error message in the kali log, so that matches = what I would expect.=20 >=20 > Yes, I was referring to the tianocore logo; I was writing that in the ka= li compiled log there are additional lines relating to tftpDynamicCommand.e= fi and LinuxInitrdDynamicShellCommand.efi, which are not in the mac compile= d log. >=20 > It sounds like you are talking about a logo coming from your Hackintosh = EFI boot shim? Or the macOS booter? > This is all the Hackintosh stuff that is loading.=20 > [Bds] Expand PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x2,0xFFFF,0x0) -> PciRoot(= 0x0)/Pci(0x1F,0x2)/Sata(0x2,0xFFFF,0x0)/HD(1,GPT,58F0B968-76EA-4F98-BD18-44= DC6D57AEBA,0x800,0x7F7DF)/\EFI\BOOT\BOOTX64.EFI > Loading driver at 0x0007DDEB000 EntryPoint=3D0x0007DDEFE36 Bootstrap.efi > Loading driver at 0x0007DC77000 EntryPoint=3D0x0007DCED3A5 OpenCore.efi > Loading driver at 0x0007DDDA000 EntryPoint=3D0x0007DDDA5C9 AE4C11C8-1D6C= -F24E-A183-E1CA36D1A8A9.efi > Loading driver at 0x0007F88E000 EntryPoint=3D0x0007F8920BD OpenRuntime.e= fi > Loading driver at 0x0007DD45000 EntryPoint=3D0x0007DD56C4B OpenCanopy.ef= i > Loading driver at 0x0007DD66000 EntryPoint=3D0x0007DD6FC53 AudioDxe.efi > Loading driver at 0x0007DDCE000 EntryPoint=3D0x0007DDD17C9 UsbMouseDxe.e= fi > Loading driver at 0x0007D054000 EntryPoint=3D0x0007D0A220C apfs.efi >=20 > And this is the macOS booter (1st stage OS loader, the thing Mac EFI fir= mware loads directly)=20 > Loading driver at 0x0007CE48000 EntryPoint=3D0x0007CE51673 boot.efi > > Yes, I know and this is expected behavior, I was not referring to that l= ogo. >=20 > There was some work on a CLANGPDB toolchain that worked on all platforms= .=20 >=20 > Thanks for this, I rapidly had a look at the github page; so these comma= nds: > $ wget https://releases.llvm.org/9.0.0/clang+llvm-9.0.0-x86_64-darwin-ap= ple.tar.xz > $ tar -xvf clang+llvm-9.0.0-x86_64-darwin-apple.tar.xz > $ git clone https://github.com/tianocore/edk2.git > $ cd edk2 > $ git clean -ffdx > $ git reset --hard > $ git submodule deinit --force --all > $ git checkout edk2-stable202008 > $ git checkout CLANGPDB > $ git submodule update --init --force > $ source edksetup.sh > $ export CLANG_BIN=3D~/my/local/path/to/clang+llvm-9.0.0-x86_64-darwin-a= pple/bin/ > $ build -a X64 -b RELEASE -p OvmfPkg/OvmfPkgX64.dsc -t CLANGPDB >=20 > will let me install the clang 9.0 toolchain in my mac os and build edk2 = with that toolchain? >=20 > So it sounds like you have some kind of graphics issue on a RELEASE buil= d? What happens if on a RELEASE XCODE build you just boot to the UEFI Shell= ? >=20 > Maybe I misunderstood, but I cannot boot to a shell, as soon as I type "= virsh start mymv" the screen goes black (with hdmi unplugged). >=20 I=E2=80=99m wondering what happens if you boot another guest OS. At least = on OVMF if you don=E2=80=99t have a guest OS to boot then you drop into an = UEFI Shell (EFI Application) that is built into the EFI ROM.=20 Thanks, Andrew Fish >=20 --Apple-Mail=_7D63F6C4-8ACF-4D40-A9E9-5C862514A607 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

On Oct 16, 2= 020, at 12:24 PM, Daniele Crudo <crudo.daniele@gmail.com> wrote:


Sorry I missed the edk2-devel in cc, res= ending.

OK so the DEBUG a= nd RELEASE both build with -Os. This is firmware things have to fit in the = ROM. The big difference between DEBUG and release is the DEBUG prints get s= tripped out, so that usually means timing issues :(. 

The compiler flags= live in  BaseTools/Conf/tools_def.template and you can edit them= in Conf/tools_def.txt

ok, thanks for this, I was hoping in optimization = issue but it seems it's not the case (?)

<= div class=3D"">
What logo are your talking about? I see the = TianoCore logo failed in your macOS debug log as I would expect [1]d:
=
"HII Image Package with logo not found in P= E/COFF resource section=E2=80=9D
I don=E2=80=99t see t= hat error message in the kali log, so that matches what I would expect.&nbs= p;

Yes, I was referring to the tianocore logo; I was writing = that in the kali compiled log there are additional lines relating to t= ftpDynamicCommand.efi and LinuxInitrdDynamicShellCommand.efi, which are not= in the mac compiled log.

=
It sounds like you ar= e talking about a logo coming from your Hackintosh EFI boot shim? Or the ma= cOS booter?
This is all the Hackintosh stuff that is l= oading. 
[Bds] Expand PciRoot(0x0= )/Pci(0x1F,0x2)/Sata(0x2,0xFFFF,0x0) -> PciRoot(0x0)/Pci(0x1F,0x2)/Sata(= 0x2,0xFFFF,0x0)/HD(1,GPT,58F0B968-76EA-4F98-BD18-44DC6D57AEBA,0x800,0x7F7DF= )/\EFI\BOOT\BOOTX64.EFI
Loading driver at 0x0007DDEB000 EntryPoint=3D0x0007DDEFE36 Bootstrap.efi<= /div>
Loading driver at 0x0007DC77000 EntryPoint=3D0x0007DCE= D3A5 OpenCore.efi
Loading driver at 0x0007DDDA000 Entr= yPoint=3D0x0007DDDA5C9 AE4C11C8-1D6C-F24E-A183-E1CA36D1A8A9.efi
Loading driver at 0x0007F88E000 EntryPoint=3D0x0007F8920BD OpenRu= ntime.efi
Loading driver at 0x0007DD45000 EntryPoint= =3D0x0007DD56C4B OpenCanopy.efi
Loading driver at 0x0= 007DD66000 EntryPoint=3D0x0007DD6FC53 AudioDxe.efi
Loa= ding driver at 0x0007DDCE000 EntryPoint=3D0x0007DDD17C9 UsbMouseDxe.efi
Loading driver at 0x0007D054000 EntryPoint=3D0x0007D0A220= C apfs.efi

And this is the macOS booter (1st stage OS loader, the thing Mac EFI= firmware loads directly) 
Loadin= g driver at 0x0007CE48000 EntryPoint=3D0x0007CE51673 boot.efi
 
Yes, I know and this is expected behavior, I was not referring to th= at logo.

T= here was some work on a CLANGPDB toolchain that worked on all platforms.&nb= sp;

Thanks for this, I rapidly had a look at the github page; so th= ese commands:
$ wget https://releases.llvm.org/9.0.0/clang+llvm-9.0.0-x86_64-darwin-app= le.tar.xz
$ tar -xvf clang+llvm-9.0.0-x86_64-darwin-apple= .tar.xz
$ git clone https://github.com/tianocore/edk2.git
$ cd = edk2
$ git clean -ffdx
$ git reset --har= d
$ git submodule deinit --force --all
$ git ch= eckout edk2-stable202008
$ git checkout CLANGPDB
$ git submodule update --init --force
$ source edkse= tup.sh
$ export CLANG_BIN=3D~/my/local/path/to/clang+llvm-9.0= .0-x86_64-darwin-apple/bin/
$ build -a X64 -b RELEASE -p Ovmf= Pkg/OvmfPkgX64.dsc -t CLANGPDB

will let me install the clang 9.0 toolchain in= my mac os and build edk2 with that toolchain?

So it sounds like you have some kind= of graphics issue on a RELEASE build? What happens if on a RELEASE XCODE b= uild you just boot to the UEFI Shell?

Maybe I misunderstood, but I = cannot boot to a shell, as soon as I type "virsh start mymv" the screen goe= s black (with hdmi unplugged).


I= =E2=80=99m wondering what happens if you boot another guest OS. At least o= n OVMF if you don=E2=80=99t have a guest OS to boot then you drop into an U= EFI Shell (EFI Application) that is built into the EFI ROM. 

Thanks,

Andr= ew Fish


--Apple-Mail=_7D63F6C4-8ACF-4D40-A9E9-5C862514A607--