Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

deeveedee
deeveedee
Posted
Posted
2 hours ago, Jief_Machak said:

 ... I can't do everything...

Try as you might to change my perception of you, you're not going to change it.  I'm convinced you can do everything! :)

  • Like 1
LAbyOne
LAbyOne
Posted
Posted
1 hour ago, matxpa said:

If you want the last Clover XCODE8 Release based on commit "f17a05f" (see attachement, Clover64.efi only). if you want or need "Clover_r5129.pkg", pkg based on commit "f17a05f", ask for it.

CloverX64-RELEASE_XCODE8-20210210164002-f17a05f-dirty.zip 701.93 kB · 0 downloads

Thanks for your offer

but i'm just trying to understand what's happening with (my) build

since apparently you all can succeed. :(

Jief_Machak
Jief_Machak
Posted
Posted
3 hours ago, LAbyOne said:

Well @Jief_Machak just to let you know r5129 (f17a05f1d)

something went really wrong here.

on all machines

10.13.6 XCode 10.1

10.14.6 XCode 11.3

10.15.7 XCode 12.4 


Processing meta-data .
Architecture(s)  = X64
Build target     = RELEASE
Toolchain        = XCODE8

Active Platform          = /Users/labyone/src/Clover/Clover.dsc
...........build: : warning: Module MetaFile [Sources] is missing local header!
    Local Header: /users/labyone/src/clover/refit_uefi/cpp_unit_test/config-test.h not found in /Users/labyone/src/Clover/rEFIt_UEFI/refit.inf
build: : warning: Module MetaFile [Sources] is missing local header!
    Local Header: /users/labyone/src/clover/refit_uefi/cpp_unit_test/config-test.h not found in /Users/labyone/src/Clover/rEFIt_UEFI/refit.inf
build: : warning: Module MetaFile [Sources] is missing local header!
    Local Header: /users/labyone/src/clover/refit_uefi/include/dsdtfixlist.h not found in /Users/labyone/src/Clover/rEFIt_UEFI/refit.inf
build: : warning: Module MetaFile [Sources] is missing local header!
    Local Header: /users/labyone/src/clover/refit_uefi/include/dsdtfixlist.h not found in /Users/labyone/src/Clover/rEFIt_UEFI/refit.inf
build: : warning: Module MetaFile [Sources] is missing local header!
    Local Header: /users/labyone/src/clover/refit_uefi/cpp_unit_test/xml_lite-test.h not found in /Users/labyone/src/Clover/rEFIt_UEFI/refit.inf
build: : warning: Module MetaFile [Sources] is missing local header!
    Local Header: /users/labyone/src/clover/refit_uefi/cpp_unit_test/xml_lite-test.h not found in /Users/labyone/src/Clover/rEFIt_UEFI/refit.inf
build: : warning: Module MetaFile [Sources] is missing local header!
    Local Header: /users/labyone/src/clover/refit_uefi/platform/posix/strings.h not found in /Users/labyone/src/Clover/rEFIt_UEFI/refit.inf
build: : warning: Module MetaFile [Sources] is missing local header!
    Local Header: /users/labyone/src/clover/refit_uefi/platform/posix/strings.h not found in /Users/labyone/src/Clover/rEFIt_UEFI/refit.inf
. done!
Building ... /Users/labyone/src/Clover/Library/MemLogLibDefault/MemLogLibDefault.inf [X64]
Building ... /Users/labyone/src/Clover/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint.inf [X64]
Building ... /Users/labyone/src/Clover/MdePkg/Library/UefiLib/UefiLib.inf [X64]
[CC] MemLogLib
Building ... /Users/labyone/src/Clover/MdePkg/Library/BasePciLibCf8/BasePciLibCf8.inf [X64]
[CC] DriverEntryPoint
clang: error: argument unused during compilation: '-mabi=ms' [-Werror,-Wunused-command-line-argument]
make: *** [/Users/labyone/src/Clover/Build/Clover/RELEASE_XCODE8/X64/Library/MemLogLibDefault/MemLogLibDefault/OUTPUT/MemLogLib.obj] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/labyone/src/Clover/Build/Clover/RELEASE_XCODE8/X64/Library/MemLogLibDefault/MemLogLibDefault]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/labyone/src/Clover/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/labyone/src/Clover/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/UefiLib/UefiLib]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/labyone/src/Clover/Build/Clover/RELEASE_XCODE8/X64/MdePkg/Library/BasePciLibCf8/BasePciLibCf8]


build.py...
 : error F002: Failed to build module
	/Users/labyone/src/Clover/Library/MemLogLibDefault/MemLogLibDefault.inf [X64, XCODE8, RELEASE]

- Failed -
Build end time: 17:05:43, Feb.10 2021
Build total time: 00:00:13

iMac:Clover labyone$

but i guess i will stick to GCC

 

That is really strange "argument unused" !
 

use V=1 before you compilation command. Like "V=1 ./buildme", or "V=1 ./ebuild.sh ..." and send me the log. I'd like to see which command exactly is producing that result.

You can also try to do "rm -r Build/" before launching your build.

PS : the warning are not the problem.

  • Like 1
LAbyOne
LAbyOne
Posted
Posted
2 hours ago, Jief_Machak said:

 

That is really strange "argument unused" !

indeed.. 

strange also because only appeared after last commit.

 

2 hours ago, Jief_Machak said:

use V=1 before you compilation command. Like "V=1 ./buildme", or "V=1 ./ebuild.sh ..." and send me the log. I'd like to see which command exactly is producing that result.

you mean the files inside Config folder

as no other log is produced during execution.

Jief_Machak
Jief_Machak
Posted
Posted
10 hours ago, Jief_Machak said:

PS : the warning are not the problem.

Ok, I was too quick to say these warnings is not a problem. It happens sometime that refit.inf is not up to date with headers list. But in this case, these files exist in the repo. The fact you don't have them IS a problem.

 

Sorry to say it again, but when you have a clear message like "Local Header: blabla.h not found", please do a little diagnostic yourself before asking... It'll save time for everyone.

So you have to fix your repo.

To understand what's going on your repo, you have "git log", "git status", "git reset", "git clean -f -f -d", for example.

  • Like 2
MacKonsti
MacKonsti
Posted
Posted

Hi everyone, although I do not fully understand the compilation issues faced, I hope you were able to resolve them!

 

Back to an issue seen on the official r5129 release (from Git Hub) when installed the Catalina Supplemental update yesterday.

Although after those couple of (fast) reboots Clover would pick up the correct partition to automatically load, for the last part of the update process, Clover did not auto-boot from the needed partition.

I realised because the hack was waiting for a selection via keyboard. I think it was the "Data" partition.

 

Has this behaviour been referenced before, hence the issue also seen on Big Sur automatic selection of that "Data" partition containing some boot files?

I have a perfectly working Clover 5129, simple setup, on macOS on the boot drive, no other OS on the system.

 

But as this is an Apple update, I cannot redo the process in order to capture logs.

Did anyone else update to Catalina supplemental Security Updates yesterday and faced the same issue with official Clover r5129 from Git Hub?

 

Thanks.

  • Confused 1
iCanaro
iCanaro
Posted
Posted
5 minutes ago, MacKonsti said:

Did anyone else update to Catalina supplemental Security Updates yesterday and faced the same issue with official Clover r5129 from Git Hub?

I updated on 4 hacks, but I did not detect such a problem, but it must be said that I am using Clover compiled and updated to the latest commits

  • Like 1
MacKonsti
MacKonsti
Posted
Posted (edited)

Thanks @iCanaro I know you guys are compiling almost on a daily basis :D but not everyone can do this and we rely on the official releases that are supposed to be stable and final.

 

Thanks @Slice and @Jief_Machak for your decision to release officially r5130, looking forward to the Git Hub notification; please be so kind to not forget to enumerate all fixes as short bullet-lists! (there are way too many pages here, perhaps consider a different thread for Clover compilation problems and keep this only for operational-functional problems?)

 

Warm regards!

Edited by MacKonsti
  • Like 1
  • Confused 1
iCanaro
iCanaro
Posted
Posted (edited)

communication, the exchange of ideas and problems allows developers to find solutions, even those related to the compilation of

if you need any "beta" clover just scroll through the thread and find some compiled

Edited by iCanaro
  • Like 1
  • Thanks 1
  • Haha 1
Jief_Machak
Jief_Machak
Posted
Posted

I've just committed a refactor of SETTINGS_DATA (which is far from finished). Mainly the ACPI section/

Maybe some of you can make some tests. I propose :

  - save your ACPI from macOS (with maciasl for example) as source text (not compiled)

  - boot the last commit

  - save the new ACPI as source test.

  - check they are both the same...

@Slice Not sure there is much new in the current release. Few things about ordering and hiding icons in the menu. No problem if we want to release it. I'll prepare a spreadsheet and post in the "test" thread.

  • Like 2
iCanaro
iCanaro
Posted
Posted

but here you don't see all the various commits performed? so even the various solutions and fixes

https://github.com/CloverHackyColor/CloverBootloader/actions

 

I compiled now with last substantial changes, all right, Clover was churned out without any problems, now the text on a hack... cross finder :) 

  • Like 2
Matgen84
Matgen84
Posted
Posted
12 minutes ago, Jief_Machak said:

I've just committed a refactor of SETTINGS_DATA (which is far from finished). Mainly the ACPI section/

Maybe some of you can make some tests. I propose :

  - save your ACPI from macOS (with maciasl for example) as source text (not compiled)

  - boot the last commit

  - save the new ACPI as source test.

  - check they are both the same...

@Slice Not sure there is much new in the current release. Few things about ordering and hiding icons in the menu. No problem if we want to release it. I'll prepare a spreadsheet and post in the "test" thread.


Ok. I'm ready for testing. Wait Google sheet or unnecessary !

Sorry for my bad English: save my ACPI = remove it from ACPI folder before boot ?

  • Like 1
Jief_Machak
Jief_Machak
Posted
Posted
9 minutes ago, Matgen84 said:


Ok. I'm ready for testing. Wait Google sheet or unnecessary !

Sorry for my bad English: save my ACPI = remove it from ACPI folder before boot ?

No. You boot with your current Clover. Launch maciasl, get your DSDT with the menu "File -> new from ACPI -> DSDT". Then save as "disassembled ASL file".

iCanaro
iCanaro
Posted
Posted
4 minutes ago, Jief_Machak said:

Are they the same ?

no, 2 different versions of Clover were used.
5129 (master, commit 8209394af) corresponds to this https://github.com/CloverHackyColor/CloverBootloader/commit/8209394af9c2106a9bfa8f4401ae996f4a248d47

LAbyOne
LAbyOne
Posted
Posted
5 hours ago, Jief_Machak said:

Ok, I was too quick to say these warnings is not a problem. It happens sometime that refit.inf is not up to date with headers list. But in this case, these files exist in the repo. The fact you don't have them IS a problem.

 

Sorry to say it again, but when you have a clear message like "Local Header: blabla.h not found", please do a little diagnostic yourself before asking... It'll save time for everyone.

So you have to fix your repo.

To understand what's going on your repo, you have "git log", "git status", "git reset", "git clean -f -f -d", for example.

 

Well " all the header files are in place ".

i did in fact re-cloned the repo twice the from within Clover i did as you asked  "V=1 ./build me" = same  error

tried also "V=1 ./ebuild.sh -fr -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t " = same  error

i guess more then cloning again and again there's nothing really i can do..

then, and sorry to point that out, but this occurred after your changes, before all worked fine on all machine but the one with cata and xcode 12

Sorry for wasting your time then.

  • Sad 1
Matgen84
Matgen84
Posted
Posted

@Jief_Machak @iCanaro

There are identical: 

 

Test r5129 commit 8209394af

  • Extract origin with F4 ------>save as DSDT-F4.dsl
  • Extract with MacIASL ----> save System DSDT_MacIasl.asl

System DSDT_MacIASL.dsl DSDT-F4.dsl

Slice
Slice
Posted
Posted
1 hour ago, Jief_Machak said:

I've just committed a refactor of SETTINGS_DATA (which is far from finished). Mainly the ACPI section/

Maybe some of you can make some tests. I propose :

  - save your ACPI from macOS (with maciasl for example) as source text (not compiled)

  - boot the last commit

  - save the new ACPI as source test.

  - check they are both the same...

@Slice Not sure there is much new in the current release. Few things about ordering and hiding icons in the menu. No problem if we want to release it. I'll prepare a spreadsheet and post in the "test" thread.

There was a mistake in release 5129 in default settings so I want to upload more correct release.

But now I see one more mistake and will fix it tonight.

  • Like 2
 Share
Go to topic listing
×
×
  • Create New...