Clover General discussion

[MakAsrock]

 

8 hours ago, Matgen84 said:

Hi all Devs

 

Try to use gcc16.1  But I can't build Clover with these settings and Default Toolchian GCC161: build error 4000 gcc161 not defined etc.

if [[ $MYTOOLCHAIN == GCC* ]] && [[ ! -x "${GCC161_BIN}" ]]; then
    if [[ $MYTOOLCHAIN == GCC161 ]]; then
      cd "${CLOVERROOT}"
      ./build_gcc16.sh
    else
      MYTOOLCHAIN=XCODE16
    fi
  fi

 

 

 

I take a look at the repo and see :

if [[ $MYTOOLCHAIN == GCC* ]] && [[ ! -x "${GCC152_BIN}" ]]; then
    if [[ $MYTOOLCHAIN == GCC152 ]]; then
      cd "${CLOVERROOT}"
      ./build_gcc16.sh
    else
      MYTOOLCHAIN=XCODE16
    fi
  fi

I can't build too if Default ToolChain is GCC161.

 

I don't understand why Default ToolChain must be GCC152 !!! 

  Reveal hidden contents

---------------------------------------------------------------------------------

                           🍀 Clover r5172 (SHA: 9af58b239)

                              Default TOOLCHAIN: GCC152

                     Switch to XCODE select: build (with XCode)

     Depending on your XCODE version the Toolset will be automatically chosen

---------------------- Current Python version: Python 3.14.6 --------------------

 

 

1) build Clover (Default Toolchain)    😎 build Clover (with XCode)

2) build all (Default Toolchain)       9) build all (with XCode)

3) make Release (Default Toolchain)   10) make Release (with XCode)

4) update Clover       11) build Clover with HFSPlus

5) make pkg       12) Extra Options

6) make iso       13) Exit

7) make Clover_V2

 

Please enter your choice:

 

So Buildme use gcc152 parameters instead of gcc161 :

  Reveal hidden contents

Running edk2 build for CloverX64 using the command:

build --cmd-len=50000 -D NO_GRUB_DRIVERS_EMBEDDED -D LESS_DEBUG --conf=/Users/mathieu/src/CloverBootloader/Conf -D USE_LOW_EBDA -D ENABLE_MODERN_CPU_QUIRKS -p Clover.dsc  -a X64 -b RELEASE -t GCC152 -n 9

 

Because GCC 16.1 was not yet implemented.
After Shabbat is over, this will be published.

Edited Saturday at 12:49 AM by MakAsrock

[Max.1974]

 

[MakAsrock]

On 7/4/2026 at 2:18 AM, MakAsrock said:

 

Because GCC 16.1 was not yet implemented.
After Shabbat is over, this will be published.

Release 5174 published (GCC 16.1 full implemented).

Edited yesterday at 04:40 AM by MakAsrock

[Max.1974]

3 hours ago, MakAsrock said:

Release 5174 published (GCC 16.1 implemented).

Thanks my friend!!  

 

 

 

 

[MakAsrock]

4 hours ago, Max.1974 said:

Thanks my friend!!  

 

 

 

 

Anytime! Hope it works smoothly for you. 🤗

Edited yesterday at 01:37 AM by MakAsrock

[MakAsrock]

Release 5174 GCC 16.1 full implementation.
 

Advanced SVG graphics, more fast more exact.
Repaired feature that SMBIOS choosing automatically according to OS version.
Using gcc-16.1.0 as main compiler.

MD5 (Clover_r5174.pkg) = 328c3aefe1ef80c724898c8f03d9cc96

What's Changed

• Bump softprops/action-gh-release from 2 to 3 by dependabot [bot] in #821
• Enhance README with logo and CI badge by @YBronst in #823
• Add Clover logo by @chris1111 in #824
• Bump actions/checkout from 6 to 7 by by dependabot [bot] in #828
• Fix unused variable build error in nanosvg.cpp by @chris1111 with @Copilot in #829
• Update build script to use GCC 16 by @YBronst in #831
• Full Changelog: #832

 

🏅 Hall of Fame (Special Thanks):

• Slice – for project general management and dedication.
• YBronst – for menu refactoring, Quirks layout implementation, audio/GUI bug fixes and GCC 16.1 full implementation.
• chris1111 – for the Tahoe/Christmas and other Themes assets.
• Hnanoto – for ModernCPUquirk, completing PT-BR (Brazilian Portuguese) translations, and resolving UI build warnings. 🇧🇷

Edited yesterday at 05:05 AM by MakAsrock

[Alpha22]

[Max.1974]

@MakAsrock  thanks!! 

 

 

 

 

[LockDown]

@MakAsrock

Yours is up by 1 version but still synced to slice's repo right?

[Max.1974]

Compiling with GCC16.1.0 smooth too  

 

 

Edited 13 hours ago by Max.1974

[MakAsrock]

3 hours ago, LockDown said:

@MakAsrock

Yours is up by 1 version but still synced to slice's repo right?

Yes, that's right. And I'm waiting for my pull request to be approved.

[LockDown]

8 hours ago, MakAsrock said:

Release 5174
Repaired feature that SMBIOS choosing automatically according to OS version.

@MakAsrock 

I was under the impression that if you leave SMBIOS empty in config.plist, Clover will detect my OS and choose a compatible smbios. But why is it clover have chosen iMac18,1 on my Tahoe which is not compatible for Tahoe?

Unless i misundertood the changelog

Edited 19 hours ago by LockDown

[MakAsrock]

6 hours ago, LockDown said:

@MakAsrock 

I was under the impression that if you leave SMBIOS empty in config.plist, Clover will detect my OS and choose a compatible smbios. But why is it clover have chosen iMac18,1 on my Tahoe which is not compatible for Tahoe?

Unless i misundertood the changelog

The changelog is accurate, but automatic SMBIOS selection is a hardware-matching heuristic, not magic. Clover chose iMac18,1 because it detected your Intel HD 620/630. For desktop Macs, iMac18,1 is the last profile where this IGPU works as the primary display output.

Clover couldn't automatically choose iMac20,1 or 20,2 for Tahoe because Apple completely disabled the integrated Intel UHD 630 on those models at the factory level (they rely exclusively on AMD dGPUs). Forcing iMac20,x on an IGPU-only desktop would result in a black screen.

The only real Macs with a working HD 630 on Tahoe are laptops (MacBookPro16,1 / 16,4), but Clover won't automatically assign a mobile profile to a desktop configuration.

Leaving SMBIOS empty is always a gamble on newer macOS versions. If you want to boot Tahoe on this hardware, you must manually specify a compatible SMBIOS in your config.plist and inject the required device-id patches as described in Clover_Of_Khaki_Color_5172-en.pdf.

Edited 15 hours ago by MakAsrock

[LockDown]

Thanks for the clarification. So would say that it's more of a hardware based detection rather than OS.

 

Im saying this due to macos not allowing you to do "fresh" install with unsupported smbios even with no_compat_check or Skip Board ID Check

Edited 8 hours ago by LockDown

[MakAsrock]

8 hours ago, LockDown said:

Thanks for the clarification. So would say that it's more of a hardware based detection rather than OS.

 

Im saying this due to macos not allowing you to do "fresh" install with unsupported smbios even with no_compat_check or Skip Board ID Check

If you try to boot the macOS Tahoe installer without a Metal 3-supported discrete graphics card, you will completely lose display output with UHD 630 or 620 (the screen goes black). Furthermore, the -no_compat_check boot-arg no longer works in Tahoe, and even if it did, a clean install is simply not possible with it.

Edited 1 hour ago by MakAsrock