From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-lf1-f44.google.com (mail-lf1-f44.google.com [209.85.167.44]) by mx.groups.io with SMTP id smtpd.web11.24377.1602876264536980231 for ; Fri, 16 Oct 2020 12:24:24 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=AI9svicF; spf=pass (domain: gmail.com, ip: 209.85.167.44, mailfrom: crudo.daniele@gmail.com) Received: by mail-lf1-f44.google.com with SMTP id l28so4336901lfp.10 for ; Fri, 16 Oct 2020 12:24:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=B17TM4AiszRKsFKHhwInYgTSX6emkNtJ2x+gQD6in34=; b=AI9svicFnV4C8lUEm+RWkwGKBLgSgrf5uIn8gWZ3uXfqyEpoz0xc1CNIAXqTUJ/xle SJG4IjBJ2SjJyrJucy82YdplhZWw60rwrYpczirQbX6aCTz3efcPYO3NbJZoXWjDfpAf bOUK/nWLfqNAGFTIAaklzDdhOgihlh1yGRF6WN0v37C/dJ+1b/ilqLKPdZxmdN/nG3uJ tmBJ6PV172cmYyqyMeKEu12fF+qnt9dzZNzR162lxcPuKzFueuzmtvtb05xfOJqKs9J2 rJnSUibpVOhPzKyo2pWS7h6cTqKlNnRo8KIBIgJgLwJVazUqfyu3fFz4rYFMfMTe1seb yz4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=B17TM4AiszRKsFKHhwInYgTSX6emkNtJ2x+gQD6in34=; b=rTD2+4NKOoITDufbsytGu0+Q8qPky1NwVkj4rQDedJTM6WTo4MK9fzEVa36JYluIFc eFUno4leQqz4uT3Ny/XAZna0KgWVQloqVM+WWoR5XEae6BWHvwdaAx8V1ojeKvbjS8qC iczvdsOBHP7S2NuE7IlvYAS/NBXoJwlpy+JnKZU0C4OMs8wEvLDCKXu6NADqe0Wulm/s RgijEnQFtoCcRo7WBe+0Q2mLN3xI2M561yjYUfKmS5gJRzJbJhOxHMM0ldcKRLAPrmSv uDB7XxZOCqChnWBk2iyStgaJ4AR19ipWoC3/nxqXZVAR36FKuApGoKCwFzr4t5ivLJjk zjPA== X-Gm-Message-State: AOAM530lpwt1BAjqEY0kM61FEy++LJ+7Z22mC8PHmVqy/Nkub+EaLH+B H43krCrZGGMm+a8mRKmyoE55iVrb1riv6ubkWos= X-Google-Smtp-Source: ABdhPJza9D/MbNlRVabr57FzGJktF6BE4XE1vYS4C2silcYxcnpNBG430k4VMSTw2JqkyQPDBaHWwq4+EchojiHyZ+s= X-Received: by 2002:a05:6512:3089:: with SMTP id z9mr1911000lfd.275.1602876262837; Fri, 16 Oct 2020 12:24:22 -0700 (PDT) MIME-Version: 1.0 References: <1D62256C-60B6-4453-AA33-1DCF7E125DD9@apple.com> In-Reply-To: From: "Daniele Crudo" Date: Fri, 16 Oct 2020 21:24:11 +0200 Message-ID: Subject: [edk2-devel] Issues with edk2 compilation with xcode5 on mac OS - files compiled but strange behaviors To: Andrew Fish Cc: edk2-devel-groups-io Content-Type: multipart/alternative; boundary="00000000000043f3eb05b1ceb64d" --00000000000043f3eb05b1ceb64d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sorry I missed the edk2-devel in cc, resending. 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 t= he > DEBUG prints get stripped 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 (?) 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 PE/COFF resource section=E2=80= =9D > I don=E2=80=99t see that error message in the kali log, so that matches w= hat I > would expect. > Yes, I was referring to the tianocore logo; I was writing that in the kali compiled log there are additional lines relating to tftpDynamicCommand.efi and LinuxInitrdDynamicShellCommand.efi, which are not in the mac compiled log. 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. > [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-4F= 98-BD18-44DC6D57AEBA,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.ef= i > Loading driver at 0x0007DD45000 EntryPoint=3D0x0007DD56C4B OpenCanopy.efi > Loading driver at 0x0007DD66000 EntryPoint=3D0x0007DD6FC53 AudioDxe.efi > Loading driver at 0x0007DDCE000 EntryPoint=3D0x0007DDD17C9 UsbMouseDxe.ef= i > Loading driver at 0x0007D054000 EntryPoint=3D0x0007D0A220C apfs.efi > > And this is the macOS booter (1st stage OS loader, the thing Mac EFI > firmware loads directly) > Loading driver at 0x0007CE48000 EntryPoint=3D0x0007CE51673 boot.efi > Yes, I know and this is expected behavior, I was not referring to that logo= . There was some work on a CLANGPDB toolchain that worked on all platforms. > Thanks for this, I rapidly had a look at the github page; so these commands= : $ wget https://releases.llvm.org/9.0.0/clang+llvm-9.0.0-x86_64-darwin-apple.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-apple/bin/ $ build -a X64 -b RELEASE -p OvmfPkg/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 build 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 goes black (with hdmi unplugged). --00000000000043f3eb05b1ceb64d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Sorry I missed the edk2-dev= el in cc, resending.

=
OK so the DEBUG and RELEASE both build with -Os. This is firmware thin= gs have to fit in the ROM. The big difference between DEBUG and release is = the DEBUG prints get stripped out, so that usually means timing issues :(.= =C2=A0

The compiler flags live in=C2=A0=C2=A0B= aseTools/Conf/tools_def.template and you can edit them in Conf/tools_def.tx= t

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

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 Pack= age with logo not found in PE/COFF resource section=E2=80=9D
I do= n=E2=80=99t see that error message in the kali log, so that matches what I = would expect.=C2=A0

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

It sounds like you are talking about a = logo coming from your Hackintosh EFI boot shim? Or the macOS booter?
<= div>This is all the Hackintosh stuff that is loading.=C2=A0
= [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.efi
Loading driver at 0x00= 07DD45000 EntryPoint=3D0x0007DD56C4B OpenCanopy.efi
Loading drive= r at 0x0007DD66000 EntryPoint=3D0x0007DD6FC53 AudioDxe.efi
Loadin= g driver at 0x0007DDCE000 EntryPoint=3D0x0007DDD17C9 UsbMouseDxe.efi
<= div>Loading driver at 0x0007D054000 EntryPoint=3D0x0007D0A220C apfs.efi

And this is the macOS booter (1st stage O= S loader, the thing Mac EFI firmware loads directly)=C2=A0
L= oading driver at 0x0007CE48000 EntryPoint=3D0x0007CE51673 boot.efi
=C2=A0
Yes, I know a= nd this is expected behavior, I was not referring to that logo.
<= br>
T= here was some work on a CLANGPDB toolchain that worked on all platforms.=C2= =A0

Thanks for this, I ra= pidly had a look at the github page; so these commands:
$ wget https://releases.llvm.org/9.0.0/clang+llvm-9.0= .0-x86_64-darwin-apple.tar.xz
$ tar -xvf clang+llvm-9.0.0-x86_64-dar= win-apple.tar.xz
$=C2=A0git clone https:= //github.com/tianocore/edk2.git
$ cd edk2
$ git cle= an -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_B= IN=3D~/my/local/path/to/clang+llvm-9.0.0-x86_64-darwin-apple/bin/
$ buil= d -a X64 -b RELEASE -p OvmfPkg/OvmfPkgX64.dsc -t CLANGPDB
will let me install the clang 9.0 toolchain in my mac os and bu= ild edk2 with that toolchain?

So it sounds like you have some kin= d of graphics issue on a RELEASE build? What happens if on a RELEASE XCODE = build you just boot to the UEFI Shell?
<= br>
Maybe I misunderstood, but I cannot boot to a shell, as soon = as I type "virsh start mymv" the screen goes black (with hdmi unp= lugged).

--00000000000043f3eb05b1ceb64d--