Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,134 posts in this topic

Recommended Posts

Jief_Machak
Jief_Machak
Posted
Posted
Just now, ameenjuz said:

please guide me clearly thanks

Sure, I can spend some time guiding you clearly, debug your EFI, but you a new SSD and deliver a computer... or I can spend some time working on Clover... I'll take the second option. Sorry but you'll have to work a bit yourself and participate.

hint : google + git init with submodule.

  • Like 1
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted (edited)

@Jief_Machak

Clover r5129 commit f17a05f1d (XCODE8) don't work on my Z390: I can't boot Big Sur 11.3 Beta.

 

From my USB, Clover GUI appears. After select BS via Preboot, return to UEFI BIOS select device.

Debug.log  is generated with bad date name : 2021-2-8_10-20-5_BOOTX64.EFI.log instead of 2021-2-10_15-00-5_BOOTX64.EFI.log

 

2021-2-8_10-20-5_BOOTX64.EFI.log

Edited by Matgen84
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
27 minutes ago, ameenjuz said:

@Jief_Machak

how to extract submodule 

please guide me clearly thanks

 

The best way: remove your local repo and git clone again.

Using this command via Terminal: git clone --recurse-submodules https://github.com/CloverHackyColor/CloverBootloader.git  YOUR_PATH

 

Replace YOUR_PATH by the correct destination

Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
6 minutes ago, Jief_Machak said:

At least you have a log now. So improvements !

I don't have any more time for next few days... But we'll debug it.

 

If you compile with GCC53, does it work ?


Very strange, works fine now more test later. But I don't know why. :wallbash:

 

First test XCODE Build: no works
Using flags: keepsyms + debug=0x100 ---> works

Using flag: debug=0x100 ---> works
No flags ---->   works

 

Thanks. Bon courage for the next few days :thumbsup_anim:
 

  • Thanks 2
Link to comment
Share on other sites
PG7
PG7
Posted
Posted

Hello team

 

step vous say good job for what you continue to do

I am a little more absent for personal reasons (greets my wife)


but I’m watching whenever I can, and I also do tests

when time permits I will be here!

 

I’m always testing and if I find any problem I’ll check

 

good continuations and that Clover always keeps on this good path

 

Spoiler

1387381042_Capturedecran2021-02-10a16_12_51.thumb.png.0d98f705664869a2738f05bbd1f0f497.png

 

  • Like 2
Link to comment
Share on other sites
LAbyOne
LAbyOne
Posted
Posted (edited)

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

Edited by LAbyOne
updated comment
  • Sad 1
Link to comment
Share on other sites
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
Link to comment
Share on other sites
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. :(

Link to comment
Share on other sites
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
Link to comment
Share on other sites
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.

Link to comment
Share on other sites
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
Link to comment
Share on other sites
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
Link to comment
Share on other sites
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
Link to comment
Share on other sites
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
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...