Badruzeus Posted June 11, 2018 Share Posted June 11, 2018 Latest Build_Clover script succeeded under Ubuntu 18.04 LTS, preboot logs seems good either. But I have a little problem when Entering any volumes on GUI; uhmmb.. Red Screen of Death immediately. Ah sorry, IDK why, looks like bcoz of unsupported system or something wrong with my local ~/src. For report only. preboot-r4532-gcc.zip Link to comment Share on other sites More sharing options...
SavageAUS Posted June 13, 2018 Share Posted June 13, 2018 Trying to build 10.14 with xcode 10 beta. Xcode is installed. Shanes-iMac:~ shane$ /Users/shane/Documents/Build_Clover.command xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance Unknown Xcode version format, exiting! Link to comment Share on other sites More sharing options...
apianti Posted June 13, 2018 Share Posted June 13, 2018 Why not use the HTTPS: prefix? works for both: https://svn.code.sf.net/p/cloverefiboot/code/ https://svn.code.sf.net/p/edk2/code/trunk/edk2 That may be why I have not experienced any issues. 3 Link to comment Share on other sites More sharing options...
Zenith432 Posted June 13, 2018 Share Posted June 13, 2018 Is it possible that just cloverefiboot repository is slow because of age and size? There are tools in svnadmin to dump repository and rebuild it with latest database format. But this needs to either be done locally on sf server with ssh access, or repository downloaded with rsync, rebuilt and then reuploaded. Link to comment Share on other sites More sharing options...
Slice Posted June 13, 2018 Share Posted June 13, 2018 On 6/12/2018 at 12:32 AM, Badruzeus said: Latest Build_Clover script succeeded under Ubuntu 18.04 LTS, preboot logs seems good either. But I have a little problem when Entering any volumes on GUI; uhmmb.. Red Screen of Death immediately. Ah sorry, IDK why, looks like bcoz of unsupported system or something wrong with my local ~/src. For report only. preboot-r4532-gcc.zip What is NASM version installed under Ubuntu? Link to comment Share on other sites More sharing options...
Zenith432 Posted June 13, 2018 Share Posted June 13, 2018 On 6/12/2018 at 12:32 AM, Badruzeus said: Latest Build_Clover script succeeded under Ubuntu 18.04 LTS, preboot logs seems good either. But I have a little problem when Entering any volumes on GUI; uhmmb.. Red Screen of Death immediately. Ah sorry, IDK why, looks like bcoz of unsupported system or something wrong with my local ~/src. For report only. For sports, I built everything including boot6, boot7 on Fedora 28 (GCC 8.1.1, nasm 2.13.03) and installed on USB stick. All variants work (UEFI boot + both legacy boot). With -D NO_GRUB_DRIVERS -D ENABLE_USB_XHCI 1 Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted June 14, 2018 Share Posted June 14, 2018 (edited) Guys, I am using your latest Build_Clover.command script to build the most recent clover distribution. However I am left with several issues when running the script on my X299 system under Mojave, while on 10.13.5 everything works as expected... It seems that you still use 32-bit applications, which simply crash on a 64-bit only system. Could you please fix the following issue? Thanks in advance, KGP Edited June 14, 2018 by KGP-iMacPro Link to comment Share on other sites More sharing options...
Matgen84 Posted June 14, 2018 Share Posted June 14, 2018 8 minutes ago, KGP-iMacPro said: Guys, I am using your latest Build_Clover.command script to build the most recent clover distribution. However I am left with several issues when running the script on my X299 system under Mojave, while on 10.13.5 everything works as expected... It seems that you still use 32-bit applications, which simply crash on a 64-bit only system. Could you please fix the following issue? Thanks in advance, KGP Hi There is no issue here with 4.8.6 version under macOS High Sierra/ Xcode 9.4. 1 Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted June 14, 2018 Share Posted June 14, 2018 5 hours ago, Matgen84 said: Hi There is no issue here with 4.8.6 version under macOS High Sierra/ Xcode 9.4. The clover build also works fine for me under 10.13.5 (32 and 64-bit applications allowed)... But the build processes fails under 10.14 (64 bit only)... same system/same configuration ... just different system disks I don't understand the point of your quote, sorry 1 Link to comment Share on other sites More sharing options...
Badruzeus Posted June 14, 2018 Share Posted June 14, 2018 (edited) 19 hours ago, Slice said: What is NASM version installed under Ubuntu? NASM 2.13.03. Here's the complete logs when building under Ubuntu 18.04. Thanks. 17 hours ago, Zenith432 said: For sports, I built everything including boot6, boot7 on Fedora 28 (GCC 8.1.1, nasm 2.13.03) and installed on USB stick. All variants work (UEFI boot + both legacy boot). With -D NO_GRUB_DRIVERS -D ENABLE_USB_XHCI Do you have JDK installed on ur Linux system? On my case, it doesn't (and IDK if JDK is needed to build Clover with GCC). #EDIT: But @Zenith432, it forced to use GCC5.3 on my Ubuntu 18.04, nor 8.1.1 << any special method for this? Thanks. build_clover_gcc_ub18.04.zip Edited June 14, 2018 by Badruzeus Link to comment Share on other sites More sharing options...
LockDown Posted June 14, 2018 Share Posted June 14, 2018 1 hour ago, KGP-iMacPro said: I don't understand the point of your quote, sorry dyslexia 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted June 14, 2018 Share Posted June 14, 2018 2 hours ago, KGP-iMacPro said: The clover build also works fine for me under 10.13.5 (32 and 64-bit applications allowed)... But the build processes fails under 10.14 (64 bit only)... same system/same configuration ... just different system disks I don't understand the point of your quote, sorry I also don't understand (sorry for my bad english). I don't test Mojave for building Clover. AppleInsider says: " Mojave will be "the last release to support 32-bit at all." Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted June 14, 2018 Share Posted June 14, 2018 (edited) 44 minutes ago, Matgen84 said: I also don't understand (sorry for my bad english). I don't test Mojave for building Clover. AppleInsider says: " Mojave will be "the last release to support 32-bit at all." But I test clover package building under Mojave. And all 32-bit (i386) implications seem to fail. So much to the claims of apple insider, which you mention above. I mean there is a reason why I am posting the issues with Build_Clover.command. Sooner or later everybody will use it with Mojave. And by then it must work flawless. Just try to help with best intentions. Edited June 14, 2018 by KGP-iMacPro 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted June 14, 2018 Share Posted June 14, 2018 6 minutes ago, KGP-iMacPro said: But I test clover package building under Mojave. And all 32-bit (i386) implications seem to fail. So much to the claims of apple insider, which you mention above. I mean there is a reason why I am posting the issues with Build_Clover.command. Sooner or later everybody will use it with Mojave. And by then it must work flawless. Just try to help with best intentions. Xcode 10 can't compile in 32bits mode, as AppleInsider says. With Build_Clover.command, there is "Standard mode 64bits only": you can test it You can also install Xcode 9.4.1 beside Xcode 10 to compile in 32bits mode I think Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted June 14, 2018 Share Posted June 14, 2018 1 minute ago, Matgen84 said: Xcode 10 can't compile in 32bits mode, as AppleInsider says. With Build_Clover.command, there is "Standard mode 64bits only": you can test it You can also install Xcode 9.4.1 beside Xcode 10 to compile in 32bits mode I think I do use Xcode 9.4 and Build_Clover.command uses the Xcode 8 tool chain, but nevertheless Build_Clover.command fails in building the clover package under 10.14... well let’s leave it as implemented currently then.. I will not insist in improvements nobody wants. Not my beer and not my problem either in fact good luck, KGP Link to comment Share on other sites More sharing options...
bronxteck Posted June 14, 2018 Share Posted June 14, 2018 i have been compiling clover on mojave since it's release with this script with no issues using xcode 9.4. on first run it did complain about lvzn compression being too old and depreciated but that it will run so maybe that is something clover needs to look out for in the near future. 1 Link to comment Share on other sites More sharing options...
Slice Posted June 14, 2018 Share Posted June 14, 2018 12 hours ago, KGP-iMacPro said: Guys, I am using your latest Build_Clover.command script to build the most recent clover distribution. However I am left with several issues when running the script on my X299 system under Mojave, while on 10.13.5 everything works as expected... It seems that you still use 32-bit applications, which simply crash on a 64-bit only system. Could you please fix the following issue? Thanks in advance, KGP Since revision 4542 your issue should be resolved. Link to comment Share on other sites More sharing options...
Mork vom Ork Posted June 14, 2018 Share Posted June 14, 2018 (edited) got these errors on building the latest CLOVER rev4542: Spoiler [CC] SerMode [SLINK] DxeIpl [DLINK1] DxeIpl /bin/sh: /usr/local/bin/mtoc.NEW: No such file or directory make: *** [/Users/md/src/UDK2018/Build/Clover/RELEASE_XCODE8/X64/Clover/CloverEFI/OsxDxeIpl/DxeIpl/DEBUG/DxeIpl.efi] Error 127 build.py... : error 7000: Failed to execute command make tbuild [/Users/md/src/UDK2018/Build/Clover/RELEASE_XCODE8/X64/Clover/CloverEFI/OsxDxeIpl/DxeIpl] build.py... : error 7000: Failed to execute command make tbuild [/Users/md/src/UDK2018/Build/Clover/RELEASE_XCODE8/X64/MdeModulePkg/Universal/WatchdogTimerDxe/WatchdogTimer] build.py... : error 7000: Failed to execute command make tbuild [/Users/md/src/UDK2018/Build/Clover/RELEASE_XCODE8/X64/MdeModulePkg/Universal/PCD/Dxe/Pcd] build.py... : error 7000: Failed to execute command make tbuild [/Users/md/src/UDK2018/Build/Clover/RELEASE_XCODE8/X64/Clover/CloverEFI/OsxDxeCore/DxeMain] build.py... : error F002: Failed to build module /Users/md/src/UDK2018/Clover/CloverEFI/OsxDxeIpl/DxeIpl.inf [X64, XCODE8, RELEASE] - Failed - Build end time: 22:25:45, Jun.14 2018 Build total time: 00:00:18 and Spoiler [SLINK] CleanNvram [CC] AmiShimPs2Map [CC] BootFixes [CC] AmiShimEfiMap [CC] CustomSlide [CC] AmiShimKeycode [DLINK1] VerifyMsrE2 [CC] device_tree /bin/sh: /usr/local/bin/mtoc.NEW: No such file or directory make: *** [/Users/md/src/UDK2018/Build/AptioFixPkg/RELEASE_XCODE8/X64/AptioFixPkg/Application/VerifyMsrE2/VerifyMsrE2/DEBUG/VerifyMsrE2.efi] Error 127 build.py... : error 7000: Failed to execute command make tbuild [/Users/md/src/UDK2018/Build/AptioFixPkg/RELEASE_XCODE8/X64/AptioFixPkg/Application/VerifyMsrE2/VerifyMsrE2] build.py... : error 7000: Failed to execute command make tbuild [/Users/md/src/UDK2018/Build/AptioFixPkg/RELEASE_XCODE8/X64/AptioFixPkg/Application/CleanNvram/CleanNvram] build.py... : error 7000: Failed to execute command make tbuild [/Users/md/src/UDK2018/Build/AptioFixPkg/RELEASE_XCODE8/X64/AptioFixPkg/Platform/AptioInputFix/AptioInputFix] build.py... : error 7000: Failed to execute command make tbuild [/Users/md/src/UDK2018/Build/AptioFixPkg/RELEASE_XCODE8/X64/AptioFixPkg/Platform/AptioMemoryFix/AptioMemoryFix] build.py... : error F002: Failed to build module /Users/md/src/UDK2018/AptioFixPkg/Application/VerifyMsrE2/VerifyMsrE2.inf [X64, XCODE8, RELEASE] - Failed - Build end time: 22:25:52, Jun.14 2018 Build total time: 00:00:07 no matter if i use CloverBuilder 1.1.6 or Build_Clover_4.8.6.sh. Maybe it's cause by this: rev.4542 says "exclude mtoc binary from clover sources it must be in system path" <--- what does THIS mean exactly? Edited June 14, 2018 by Mork vom Ork 1 Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted June 14, 2018 Share Posted June 14, 2018 (edited) 32 minutes ago, Slice said: Since revision 4542 your issue should be resolved. Thanks @Slice! Issue solved! Seems that I am missing /Users/kgp/src/opt/local/bin/mtoc.NEW though... what should I do? In consequence I might get the build.py... errors below and still no successful clover build. I am sure the fault is at my side. Am I missing something? Sorry to bother you guys with all these problems.. Edit: Ohh I just see that @Mork vom Ork reports the same issue nearly simultaneously.. Edited June 14, 2018 by KGP-iMacPro Link to comment Share on other sites More sharing options...
vector sigma Posted June 14, 2018 Share Posted June 14, 2018 (edited) Guys, there is a bug I solved in 10.14 and Xcode 10: Build_Clover_mojave_Xcode10.command.zip, but to entirely build the pkg you need to replace all these folders in ~/src/edk2/Clover/CloverPackage/ @Slice, even fdisk440 is 64 bit, and I can make it conditional if you want (just saw only now your latest commit). Anyway need testers, and this test is for 10.14 and Xcode 10 (don't try in 10.13 or with older Xcode, this is a test only for the ltest OS and is not yet conditional) CloverPrefpane.zip CloverUpdater.zip utils.zip Edited June 14, 2018 by vector sigma Build_Clover_mojave_Xcode10.command.zip updated for mtoc.NEW 2 Link to comment Share on other sites More sharing options...
Mork vom Ork Posted June 14, 2018 Share Posted June 14, 2018 (edited) fixed it by myself by copying the attached file into "usr/local/bin". (of cause you have to unzip it before copying) Compiled Rev 4542 successfully now. MTOC.NEW.zip Attached mtoc.new file is comming from @cecekpawon GitHub page here. Edited June 14, 2018 by Mork vom Ork 2 Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted June 14, 2018 Share Posted June 14, 2018 8 minutes ago, vector sigma said: Guys, there is a bug I solved in 10.14 and Xcode 10: Build_Clover_mojave_Xcode10.command.zip, but to entirely build the pkg you need to replace all these folders in ~/src/edk2/Clover/CloverPackage/ @Slice, even fdisk440 is 64 bit, and I can make it conditional if you want. Anyway need testers. CloverPrefpane.zip CloverUpdater.zip utils.zip 1.) Delete ~/src 2.) Execute Build_Clover_mojave_Xcode10.command 3.) Replace CloverPrefpane, CloverUpdater and utils 4.) Execute Build_Clover_mojave_Xcode10.command with (5) 5.) Execute Execute Build_Clover_mojave_Xcode10.command first (2) and the with (5) In both case (4) and (5) errors depicted in my post above persist. a.) missing /Users/kgp/src/opt/local/bin/mtoc.NEW b.) build.py... errors 1 Link to comment Share on other sites More sharing options...
vector sigma Posted June 14, 2018 Share Posted June 14, 2018 (edited) 20 minutes ago, KGP-iMacPro said: 1.) Delete ~/src 2.) Execute Build_Clover_mojave_Xcode10.command 3.) Replace CloverPrefpane, CloverUpdater and utils 4.) Execute Build_Clover_mojave_Xcode10.command with (5) 5.) Execute Execute Build_Clover_mojave_Xcode10.command first (2) and the with (5) In both case (4) and (5) errors depicted in my post above persist. a.) missing /Users/kgp/src/opt/local/bin/mtoc.NEW b.) build.py... errors use this, as I said I see last commit by Slice after my modifications, no need for 1), and no need to be in /opt/local/bin in coercion even if Slice said the opposite in its latest commit (fortunately there is still a MTOC_PREFIX) Build_Clover_mojave_Xcode10.command.zip Edited June 14, 2018 by vector sigma mtoc.NEW auto install! 1 Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted June 14, 2018 Share Posted June 14, 2018 (edited) 31 minutes ago, Mork vom Ork said: fixed it by myself by copying the attached file into "usr/local/bin". (of cause you have to unzip it before copying) Compiled Rev 4542 successfully now. MTOC.NEW.zip Yup @Mork vom Ork, @Slice, @vector sigma 1.) Delete ~/src 2.) Build_clover.command v.4.8.6 3.) Build_clover.command (2) 4.) copy MTOC.NEW of @Mork vom Ork to ~/src/opt/local/bin/ 5.) Build_clover.command (5) y voila!!!! I guess the script still installs MTOC but calls MTOC.NEW Thats's all! All issues solved Edited June 14, 2018 by KGP-iMacPro 2 Link to comment Share on other sites More sharing options...
vector sigma Posted June 14, 2018 Share Posted June 14, 2018 2 minutes ago, KGP-iMacPro said: Yup @Mork vom Ork, @Slice, @vector sigma 1.) Delete ~/src 2.) Build_clover.command v.4.8.6 3.) Build_clover.command (2) 4.) copy MTOC.NEW of @Mork vom Ork to ~/src/opt/local/bin/ 5.) Build_clover.command (5) y voila!!!! I guess the script still installs MTOC but calls MTOC.NEW Thats's all! All issues solved nope, it's installed by buildmtoc.sh: cmd="install -c -s -m 555 efitools/mtoc.NEW ${PREFIX}/bin" hope you quit the script before retry Link to comment Share on other sites More sharing options...
Recommended Posts