Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,137 posts in this topic

Recommended Posts

kushwavez
kushwavez
Posted
Posted (edited)
8 hours ago, iCanaro said:

hack Z97

compilation error

 

 

mojave-10.14.6_18G8022_XCODE-11.3.1.rtf 37.38 kB · 4 downloads

This is regular ./buildme (with GCC53)

The problem is with ./buildme XCODE8 

 

For me, GCC53 is working perfectly fine on Mojave. Do a fresh clone and try again. (or just delete Tools dir)

Edited by kushwavez
  • Haha 1
  • Sad 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
10 hours ago, Jief_Machak said:

I can see it's not injected.

Don't know why, it is here on my VM.

Could you try : CloverX64-2021-04-03-23-31-49-6ff5bab-dirty-jief.zip. Check in your Base Board Information, Version must be 1.0 and not IMac19,1. Also, your serial number in "system information" was not right. If it's still the case, could you send me the debug.log and you config.plist and the dmidecode output, so I'll try to reproduce here.

Shorten manufacturer name should be fixed as well.


@Jief_Machak 12 hours ago (page #1065), I apologized: there are differences because I forgot to update the config.plist (USB test drive). Now there is no difference. 

I try the new dirty-jief efi clover anyway 

diff /Users/mathieu/Desktop/Clover\ r5132\ 96909661a-2021-04-04.txt /Users/mathieu/Desktop/CloverX64-2021-04-03-23-31-49-6ff5bab-dirty-jief.txt 
4c4
< 71 structures occupying 3088 bytes.
---
> 71 structures occupying 3027 bytes.
281c281
< 	String 1: Apple ROM Version..Board-ID : Mac-AA95B1DDAB278B95....  Powered by Clover revision: 5132 (master, commit 96909661a).
---
> 	String 1: ...  Powered by 2021-04-03-23-31-49-6ff5bab-dirty-jief.

 

 

Clover r5132 96909661a-2021-04-04.txt CloverX64-2021-04-03-23-31-49-6ff5bab-dirty-jief.txt

11 hours ago, Jief_Machak said:

I confirm this compilation option is there since some time. Maybe it's deprecated in newer version ?

I'll create a XCODE10 toolchain without this arg and we'll if that works.


@Jief_Machak Can we use XCODE10 Toolchain ! 

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
26 minutes ago, kushwavez said:

This is regular ./buildme (with GCC53)

The problem is with ./buildme XCODE8 

 

For me, GCC53 is working perfectly fine on Mojave. Do a fresh clone and try again. (or just delete Tools dir)


Hi @kushwavez I can build successfully with XCODE8 Toolchain on Mojave: menu option (13) + menu option (1). No issues.

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
31 minutes ago, kushwavez said:

@Matgen84

What are the versions?

pkgutil --pkg-info=com.apple.pkg.CLTools_Executables

gcc --version

OS, Xcode version

 

@kushwavez

 

I use Buildme script for building and make pkg  (Mojave 10.14.6 latest) Xcode 11.3.1

  

package-id: com.apple.pkg.CLTools_Executables
version: 11.3.1.0.1.1576735732
volume: /
location: /
install-time: 1612808238
groups: com.apple.FindSystemFiles.pkg-group

 

  • Thanks 1
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
15 minutes ago, kushwavez said:

@Matgen84 okay it's working now, thanks for the info. @Jief_Machak looks like the problem was that my Command Line Tools wasn't up-to-date. Mine was 10.3.0.0.1.1562985497, but the latest is 11.3.1.0.1.1576735732 but it didn't update itself. Now I updated and it's building just fine.

Mine is 

package-id: com.apple.pkg.CLTools_Executables

version: 10.3.0.0.1.1562985497

But I prefer to use GCC53.

Link to comment
Share on other sites
maclinuxG4
maclinuxG4
Posted
Posted (edited)

no boot with mac os sierra now

 

it not last version from clover, i have used kext from and old efi, i boot now (config.plist update smbios, and clover  on master brnach git).

 

it is also ok for mojave too

 

 

Edited by maclinuxG4
Link to comment
Share on other sites
kushwavez
kushwavez
Posted
Posted
2 hours ago, Slice said:

Mine is 

package-id: com.apple.pkg.CLTools_Executables

version: 10.3.0.0.1.1562985497

But I prefer to use GCC53.

hmmm.. and you can build with XCODE8 with that version?

 

idk why I couldn't. But anyways updating cltools solved the problem.

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
22 minutes ago, kushwavez said:

hmmm.. and you can build with XCODE8 with that version?

 

 

Yes, 

[GENFW] CLOVERX64

Generating DUETEFIMAINFVX64 FV
###
GUID cross reference file can be found at /Users/sergey/src/CloverBootloader/Build/Clover/RELEASE_XCODE8/FV/Guid.xref

FV Space Information
DUETEFIMAINFVX64 [36%Full] 2752512 total, 1007504 used, 1745008 free

- Done -
Build end time: 16:13:25, Apr.04 2021
Build total time: 00:01:39

  -> CloverX64-RELEASE_XCODE8-20210403174249-6ff5bab-dirty.efi

 

  • Like 2
Link to comment
Share on other sites
kushwavez
kushwavez
Posted
Posted

@Slice they're downloaded & compiled by Clover builder itself.

nasm: 

NASM version 2.15.05 compiled on Apr  4 2021

Unfortunately I don't know what version is MTOC, but named: "mtoc.NEW_jief", also downloaded by Clover buildme

They're located in ./toolchain/bin

Link to comment
Share on other sites
Slice
Slice
Posted
Posted
1 hour ago, kushwavez said:

@Slice they're downloaded & compiled by Clover builder itself.

nasm: 


NASM version 2.15.05 compiled on Apr  4 2021

Unfortunately I don't know what version is MTOC, but named: "mtoc.NEW_jief", also downloaded by Clover buildme

They're located in ./toolchain/bin

Correct.

Then I see no reason why you can't compile.

My system is Mojave. Your as well?

Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted

 

5 hours ago, kushwavez said:

Unfortunately I don't know what version is MTOC, but named: "mtoc.NEW_jief",

Yes, I had to modify that to be able to live debug with gdb. Before it was call mtoc.NEW.

Maybe we should just come back to "mtoc"...

Nothing really important here. And the unrecognized "-mabi=ms" was way before the mtoc phase.

Glad you you found the problem of command line tools. Still weird that it didn't recognize a compile flag.

  • Like 2
Link to comment
Share on other sites
Jief_Machak
Jief_Machak
Posted
Posted

Fixed.

For an unknown reason, the lto optimization decided to not align the "__beginning_of_section_ctors" symbol. I've put it in its own section with alignment.

DEBUG compilation are not optimized with lto, that's why they also worked.

  • Thanks 1
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
8 hours ago, Jief_Machak said:

Fixed.

For an unknown reason, the lto optimization decided to not align the "__beginning_of_section_ctors" symbol. I've put it in its own section with alignment.

DEBUG compilation are not optimized with lto, that's why they also worked.

But why it is happen only with new commit?

 

One more. One user reported very long pause 

13:360 0:000 add device: PciRoot(0x0)/Pci(0x1C,0x6)/Pci(0x0,0x0)
13:360 0:000 Add key=built-in valuelen=1
13:360 0:000 ATI injection not set
27:689 14:328 stringlength = 134284
27:691 0:001 CurrentMode: Width=3840 Height=2160
27:692 0:000 SetNvramVariable (FirmwareFeaturesMask, guid, 0x6, 4):
27:692 0:000 -> writing new (Success)

14 seconds at the end of Device Properties strings.

This is X79-P3 with Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz.

https://applelife.ru/threads/clover.42089/page-1363#post-934102

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...