Badruzeus Posted June 12, 2018 Share Posted June 12, 2018 (edited) Try using VPN service, I no longer get problem after it. Just built r4535 w/o issue with SF server here, or I was just lucky. Edited June 12, 2018 by Badruzeus 1 Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted June 12, 2018 Share Posted June 12, 2018 @Slice, seems that 4535 completely removed the NASM issue. Well done! However it seems that there remains another issue later on, see below: Link to comment Share on other sites More sharing options...
chris1111 Posted June 12, 2018 Share Posted June 12, 2018 No issue build Clover UDK2018 before 4532 and more I just update to 4536 now also no issue build nasm Link to comment Share on other sites More sharing options...
Sherlocks Posted June 12, 2018 Share Posted June 12, 2018 31 minutes ago, Badruzeus said: Try using VPN service, I no longer get problem after it. Just built r4535 w/o issue with SF server here, or I was just lucky. GOOD Point! 1. Mac Address(ASUS router) - i changed Mac Address, but it's not help. same issue 2. VPN - change Korea to Japan. -> it's good i think SF server limited korea internet. i don't understand it. if you have connection issue, use VPN. lol thanks to @Badruzeus 1 Link to comment Share on other sites More sharing options...
chris1111 Posted June 12, 2018 Share Posted June 12, 2018 (edited) Package build Edited June 12, 2018 by chris1111 Link to comment Share on other sites More sharing options...
Slice Posted June 12, 2018 Share Posted June 12, 2018 fdisk440 should be revised or just excluded. It is compiled to 32bit which is no more supported. There is a better way to install mbr0 sector sizeof 440 dd if=/dev/disk0 count=1 bs=512 of=origMBR cp origMBR newMBR dd if=boot0 of=newMBR bs=1 count=440 conv=notrunc dd if=newMBR of=/dev/disk0 count=1 bs=512 Someone can implement this into Clover Package? And completely exclude fdisk440. EDITED. Or /dev/rdisk0 ? 3 Link to comment Share on other sites More sharing options...
Badruzeus Posted June 12, 2018 Share Posted June 12, 2018 Guessing, this is just bug with Mojave's interface; so when Appearance=Dark, we lost Clover logo from installer package (Bottom-Left). Link to comment Share on other sites More sharing options...
chris1111 Posted June 12, 2018 Share Posted June 12, 2018 this is normal in dark mode, light mode logo is there 2 Link to comment Share on other sites More sharing options...
Badruzeus Posted June 12, 2018 Share Posted June 12, 2018 (edited) 49 minutes ago, chris1111 said: this is normal in dark mode, light mode logo is there It seems, "background.tiff" is disappeared if Appearance=Dark in Mojave. I just make this image lighter (#000000 > #666666) then rebuilt the package.. but still get same result.. Strange. ~/src/edk2/Clover/CloverPackage/package/Resources/background.tiff Edited June 12, 2018 by Badruzeus Link to comment Share on other sites More sharing options...
arsradu Posted June 12, 2018 Share Posted June 12, 2018 Hi guys, How do you clean the environment for a new build? I replaced the sources for 4535 with 4536...but it still builds 4535 for some reason. :)) I'm guessing it needs some sort of cleanup in order to get the new build but everything I tried so far didn't quite help. I already tried ./ebuild.sh cleanpkg, ./ebuild.sh cleanall, ./ebuild.sh clean... but no difference. Any idea what am I doing wrong? Or...not doing? Link to comment Share on other sites More sharing options...
Slice Posted June 12, 2018 Share Posted June 12, 2018 18 minutes ago, arsradu said: Hi guys, How do you clean the environment for a new build? I replaced the sources for 4535 with 4536...but it still builds 4535 for some reason. :)) I'm guessing it needs some sort of cleanup in order to get the new build but everything I tried so far didn't quite help. I already tried ./ebuild.sh cleanpkg, ./ebuild.sh cleanall, ./ebuild.sh clean... but no difference. Any idea what am I doing wrong? Or...not doing? You may delete folder EDK2/Build and start again. But version should be updated automatically. Check commands in terminal svnversion (yes as one word) svn info May be we have to update build script to use (svn info) Link to comment Share on other sites More sharing options...
chris1111 Posted June 12, 2018 Share Posted June 12, 2018 22 minutes ago, arsradu said: Hi guys, How do you clean the environment for a new build? I replaced the sources for 4535 with 4536...but it still builds 4535 for some reason. :)) I'm guessing it needs some sort of cleanup in order to get the new build but everything I tried so far didn't quite help. I already tried ./ebuild.sh cleanpkg, ./ebuild.sh cleanall, ./ebuild.sh clean... but no difference. Any idea what am I doing wrong? Or...not doing? Before build update you need svn up 1 Link to comment Share on other sites More sharing options...
Slice Posted June 12, 2018 Share Posted June 12, 2018 Instead of svnversion use svn info | grep "Revision" | tr -cd [:digit:] Link to comment Share on other sites More sharing options...
arsradu Posted June 12, 2018 Share Posted June 12, 2018 (edited) 7 minutes ago, Slice said: You may delete folder EDK2/Build and start again. But version should be updated automatically. Check commands in terminal svnversion (yes as one word) svn info May be we have to update build script to use (svn info) imac-2:Clover jimmy$ svnversion 4535M imac-2:Clover jimmy$ svn info Path: . Working Copy Root Path: /Users/jimmy/src/UDK2018/Clover URL: https://svn.code.sf.net/p/cloverefiboot/code Relative URL: ^/ Repository Root: https://svn.code.sf.net/p/cloverefiboot/code Repository UUID: 52d7a1c0-eba5-4e63-a9d7-e3186cd7c462 Revision: 4535 Node Kind: directory Schedule: normal imac-2:Clover jimmy$ svn info | grep "Revision" | tr -cd [:digit:] 4535imac-2:Clover jimmy$ So I guess my svn is still on 4535, which causes it to build 4535 instead of 4536. Edited June 12, 2018 by arsradu Link to comment Share on other sites More sharing options...
chris1111 Posted June 12, 2018 Share Posted June 12, 2018 1 hour ago, Badruzeus said: It seems, "background.tiff" is disappeared if Appearance=Dark in Mojave. I just make this image lighter (#000000 > #666666) then rebuilt the package.. but still get same result.. Strange. ~/src/edk2/Clover/CloverPackage/package/Resources/background.tiff No issue here light mode 1 Link to comment Share on other sites More sharing options...
Slice Posted June 12, 2018 Share Posted June 12, 2018 6 minutes ago, arsradu said: imac-2:Clover jimmy$ svn info | grep "Revision" | tr -cd [:digit:] 4535imac-2:Clover jimmy$ So I guess my svn is still on 4535, which causes it to build 4535 instead of 4536. svn up 1 Link to comment Share on other sites More sharing options...
arsradu Posted June 12, 2018 Share Posted June 12, 2018 (edited) 11 minutes ago, Slice said: svn up That brings the version to 4537 indeed. BUT I apparently run into some conflicts. A Drivers/UsbBusDxe/UsbBusDxeExtra.uni A Drivers/UsbBusDxe/UsbBus.h A Drivers/UsbBusDxe/UsbUtility.h A Conf/Tpl/MSFT/config.template A gptsync/gptsync.inf A gptsync/gptsync.h A Certificates/Default/Signing.key U . Updated to revision 4537. Summary of conflicts: Tree conflicts: 145 Tree conflict on 'BuildTools' > local dir unversioned, incoming dir add upon update Select: (r) mark resolved, (p) postpone, (q) quit resolution, (h) help: Uhm...help? :)) Or is that intended? I'm guessing this happened because the initial source was not downloaded via svn? So..it's "unversioned" because of this? And when I did the svn up it added whatever was different from my local source, but also, couldn't compare versions? I exited the Terminal and went back. Now it says only imac-2:Clover jimmy$ svn up Updating '.': At revision 4537. Edited June 12, 2018 by arsradu Link to comment Share on other sites More sharing options...
Slice Posted June 12, 2018 Share Posted June 12, 2018 Delete manually this folder and try again 2 Link to comment Share on other sites More sharing options...
Badruzeus Posted June 12, 2018 Share Posted June 12, 2018 19 minutes ago, chris1111 said: No issue here light mode Oh, I see.. now I just realize that it happened to another package installer too.. a bug with DarkMode, I think. Spoiler What a great idea from Apple to make our eyes blind, then they'll release a new device named "iGlass" #LoL 1 Link to comment Share on other sites More sharing options...
arsradu Posted June 12, 2018 Share Posted June 12, 2018 Delete manually this folder and try againYep. Works fine with a fresh environment. Which means that most likely it is/was the fact that I “injected” the Clover sources into the environment instead of downloading them from svn that caused the issues. Thank you so much for your feedback.By the way, I’m not sure who should I be thanking for this, but building Clover using UDK2018 method is a LOT faster. It is probably also faster because it doesn’t build 32 bit versions anymore. But I don’t know, it just seems really, really fast now.Well done! Link to comment Share on other sites More sharing options...
arsradu Posted June 12, 2018 Share Posted June 12, 2018 Guys, a new issue when building the package in Mojave. I'm pretty sure it's something related to the setup. I'm using Xcode 10, obviously. But...the error says Xcode version too old. Which makes no sense. 192-168-0-116:CloverPackage jimmy$ ./makepkg ========= Translating Resources ======== /Users/jimmy/src/UDK2018/Clover/CloverPackage/package/../../../../opt/local XCode version too old. Not extracting locale strings from source XIB file XCode version too old. Not extracting locale strings from source XIB file XCode version too old. Don't extracting locale strings from source files Building CloverUpdater application... [XCODE] Building CloverPrefpane preference... ** BUILD FAILED ** make: *** [CloverPrefpane] Error 65 192-168-0-116:CloverPackage jimmy$ Did anyone succeed to build Clover in Xcode 10 with this method? Link to comment Share on other sites More sharing options...
Slice Posted June 12, 2018 Share Posted June 12, 2018 1 hour ago, arsradu said: Guys, a new issue when building the package in Mojave. I'm pretty sure it's something related to the setup. I'm using Xcode 10, obviously. But...the error says Xcode version too old. Which makes no sense. 192-168-0-116:CloverPackage jimmy$ ./makepkg ========= Translating Resources ======== /Users/jimmy/src/UDK2018/Clover/CloverPackage/package/../../../../opt/local XCode version too old. Not extracting locale strings from source XIB file XCode version too old. Not extracting locale strings from source XIB file XCode version too old. Don't extracting locale strings from source files Building CloverUpdater application... [XCODE] Building CloverPrefpane preference... ** BUILD FAILED ** make: *** [CloverPrefpane] Error 65 192-168-0-116:CloverPackage jimmy$ Did anyone succeed to build Clover in Xcode 10 with this method? Show, please, output xcodebuild -version | sed -nE 's/^Xcode ([0-9]).*/\1/p' Link to comment Share on other sites More sharing options...
arsradu Posted June 12, 2018 Share Posted June 12, 2018 Just now, Slice said: Show, please, output xcodebuild -version | sed -nE 's/^Xcode ([0-9]).*/\1/p' Seems to be 1. 192-168-0-116:~ jimmy$ xcodebuild -version | sed -nE 's/^Xcode ([0-9]).*/\1/p' 1 192-168-0-116:~ jimmy$ Link to comment Share on other sites More sharing options...
KGP-iMacPro Posted June 12, 2018 Share Posted June 12, 2018 (edited) @Slice, fdisk440 32 bit error under Mojave still persists even in 4537 ... Edited June 12, 2018 by KGP-iMacPro Link to comment Share on other sites More sharing options...
Slice Posted June 13, 2018 Share Posted June 13, 2018 5 hours ago, arsradu said: Seems to be 1. 192-168-0-116:~ jimmy$ xcodebuild -version | sed -nE 's/^Xcode ([0-9]).*/\1/p' 1 192-168-0-116:~ jimmy$ I excluded Xcode version check in 4538. It was needed for Xcode 3 and 4. Now I think xcode is always >=5. If anyone want old versions then welcome with your proposition how to do better way. 6 hours ago, arsradu said: Seems to be 1. 192-168-0-116:~ jimmy$ xcodebuild -version | sed -nE 's/^Xcode ([0-9]).*/\1/p' 1 192-168-0-116:~ jimmy$ Check, please xcodebuild -version | sed -nE 's/^Xcode ([0-9]+).*/\1/p' Link to comment Share on other sites More sharing options...
Recommended Posts