Clover General discussion

[MakAsrock]

1 hour ago, MakAsrock said:

I encountered the same error with the original makeiso, makepkg, and makeV2 on Sequoia, so I rewrote all three files, slightly changing the algorithms.
This line is to blame:
revision=$(git describe --tags $(git rev-list --tags --max-count=1))

There's an invisible character (ZERO WIDTH SPACE or similar Unicode garbage) in there. Git interprets it as part of the argument, and instead of --max-count=1 , it actually gets something like --max-count=1<invisible_character> . As a result, the strange argument "1…" is substituted, and Git complains that it's not a number.

The old script is "like the original" and only works in the "correct" environment (called from Make, macOS, with a configured PATH, in a tagged Git repository).
My new script is more self-contained and robust:
it automatically finds the repo and toolchain;
it doesn't crash without tags;
it also works on Linux;
it monitors errors more accurately.
I could have limited myself to cleaning the old scripts of invisible characters, but I decided that the new algorithms were more reliable.
Slice shouldn't be harassing me. I've been programming since the days of punch cards. It's just that with age, I've lost my concentration in large volumes of program lines. If I don't write everything at once, as I used to, I rarely make mistakes.

My revised makepkg includes the following changes:
PATH has been expanded to include the local toolchain/bin
Pre-build checks for all critical tools (git, msgfmt, xgettext, make, xcode-select) have been added.
Revision is now set to the safe value unknown if there are no tags.
Otherwise, the structure and style are identical to the original.
With this script, you can run the build from anywhere, and it correctly picks up the necessary tools without manually tinkering with the PATH.
In addition, I wrote a utility that does the following:
 

================ Simple File Utility ================

What would you like to do?

1) Make a file executable

2) Remove quarantine from a file

3) Clean invisible symbols (BOM / Zero-width) in a file

4) Run a script or program

5) Exit

Choose an option (1/2/3/4/5): 

MacFileHelper.zip makepkg.zip

[Max.1974]

 

13 minutes ago, MakAsrock said:

My revised makepkg includes the following changes:
PATH has been expanded to include the local toolchain/bin
Pre-build checks for all critical tools (git, msgfmt, xgettext, make, xcode-select) have been added.
Revision is now set to the safe value unknown if there are no tags.
Otherwise, the structure and style are identical to the original.
With this script, you can run the build from anywhere, and it correctly picks up the necessary tools without manually tinkering with the PATH.
In addition, I wrote a utility that does the following:
 

================ Simple File Utility ================

What would you like to do?

1) Make a file executable

2) Remove quarantine from a file

3) Clean invisible symbols (BOM / Zero-width) in a file

4) Run a script or program

5) Exit

Choose an option (1/2/3/4/5): 

MacFileHelper.zip 2.61 kB · 0 downloads makepkg.zip 1.76 kB · 0 downloads

 

BOM (Byte Order Mark) - It's a special sequence of bytes at the beginning of a text file that indicates:

The file's encoding (UTF-8, UTF-16, UTF-32)

The byte order (little-endian or big-endian)

BOM Examples:

UTF-8 BOM: EF BB BF (3 bytes)

UTF-16 LE: FF FE (little-endian)

UTF-16 BE: FE FF (big-endian)

UTF-32 LE: FF FE 00 00

Why It Causes Problems:

Unix/Linux scripts expect text files without BOM. When a BOM is present:

# File with UTF-8 BOM hexdump -C file.txt 00000000 ef bb bf 31 0a |...1.| ^^^^^^^^ BOM ^^ "1"

The system reads EF BB BF 31 instead of just 31 (which is "1" in ASCII).

Result: fatal: '1': not an integer because it's trying to interpret 1 (BOM + 1) as a number.

How to Check if a File Has BOM:

# Method 1 file filename.txt # Shows: "UTF-8 Unicode (with BOM) text" # Method 2 hexdump -C filename.txt | head -1 # If it starts with "ef bb bf" = has UTF-8 BOM # Method 3 head -c 3 filename.txt | xxd

How to Remove BOM:

# Remove BOM from a file sed -i '' '1s/^\xEF\xBB\xBF//' filename.txt

In your case, some file related to Clover's version/revision likely has this invisible BOM, causing the error.

Edited October 3, 2025 by Max.1974

[MakAsrock]

25 minutes ago, Max.1974 said:

 

 

BOM (Byte Order Mark) - It's a special sequence of bytes at the beginning of a text file that indicates:

The file's encoding (UTF-8, UTF-16, UTF-32)

The byte order (little-endian or big-endian)

BOM Examples:

UTF-8 BOM: EF BB BF (3 bytes)

UTF-16 LE: FF FE (little-endian)

UTF-16 BE: FE FF (big-endian)

UTF-32 LE: FF FE 00 00

Why It Causes Problems:

Unix/Linux scripts expect text files without BOM. When a BOM is present:

# File with UTF-8 BOM hexdump -C file.txt 00000000 ef bb bf 31 0a |...1.| ^^^^^^^^ BOM ^^ "1"

The system reads EF BB BF 31 instead of just 31 (which is "1" in ASCII).

Result: fatal: '1': not an integer because it's trying to interpret 1 (BOM + 1) as a number.

How to Check if a File Has BOM:

# Method 1 file filename.txt # Shows: "UTF-8 Unicode (with BOM) text" # Method 2 hexdump -C filename.txt | head -1 # If it starts with "ef bb bf" = has UTF-8 BOM # Method 3 head -c 3 filename.txt | xxd

How to Remove BOM:

# Remove BOM from a file sed -i '' '1s/^\xEF\xBB\xBF//' filename.txt

In your case, some file related to Clover's version/revision likely has this invisible BOM, causing the error.

No longer contains. I did it. Clone the repository again.

Edited October 3, 2025 by MakAsrock

[Max.1974]

9 minutes ago, MakAsrock said:

No longer contains. I did it. Clone the repository again.

 

 

Hi @MakAsrock It still persists, but I believe there’s no problem using it on Tahoe Beta, as it can compile on previous macOS versions as well. If it’s only a cosmetic issue, then it’s fine. It’s running normally for me, with less than 10 seconds of boot time.  

 

I make clean installer git 

[MakAsrock]

1 hour ago, Max.1974 said:

 

 

Hi @MakAsrock It still persists, but I believe there’s no problem using it on Tahoe Beta, as it can compile on previous macOS versions as well. If it’s only a cosmetic issue, then it’s fine. It’s running normally for me, with less than 10 seconds of boot time.  

 

I make clean installer git 

Try with this.

makeV2.zip

[Max.1974]

With buildme directly, compile with python 3.13.5, same warning appears. 

 

 

I will show my compiler Builder in Ventura soon 

 

 

Edited October 3, 2025 by Max.1974

[Max.1974]

macOs Ventura, MBA 2020 T2 Chip intel i7  😄

 

It's just a warning but thanks a lot !!  

 

 

[MakAsrock]

Okay, @Max.1974. I'll keep thinking but after Shabbat. 😉

[Max.1974]

Good Shabbat for you!! Shalom !!! 

[Stefanalmare]

5 hours ago, chris1111 said:

@MakAsrock Ive not see any issue with buildme

 

@Max.1974 

This message only appears in Tahoe 26

 

Dont know why? In Sequoia and bellow thats not appear

I had this error in Sequoia with Xcode 26.0.1.

[MakAsrock]

25 minutes ago, MakAsrock said:

Friends, aren't you concerned that this error is in builder.sh? I don't have that file, and I can't reproduce the error on any macOS. This isn't a glitch with Taha or my buildme. Perhaps it doesn't reproduce for me because I don't allow HomeBrew on my computer. Ошибка исчезла после ручного удаления Python 3.13.5, HomeBrew и испорченного ими Python 3.13.7 а затем последующей установкой Python 3.13.7 с официального сайта. I haven't been able to stand HomeBrew for about 10 years now. I myself use MacPort for two programs: 7zz and Midnight Commander. So I consider this Issue closed for the time being. If anything happens, open it in the repo on GitHub and we'll figure it out.

 

Edited October 3, 2025 by MakAsrock

[MakAsrock]

3 hours ago, Stefanalmare said:

I had this error in Sequoia with Xcode 26.0.1.

I can’t test it on Xcode 26.1 because my Tahoe is not connected to the network. There is physically nowhere to insert a network cable.

 

Edited October 3, 2025 by MakAsrock

[chris1111]

4 hours ago, Stefanalmare said:

I had this error in Sequoia with Xcode 26.0.1.

Ok great I have also Xcode 16 in Tahoe I will test then let you know

 

EDIT*** Culprit is Xcode 26

 

Using Command Line Tools Xcode 16.4 no issue

 

 

My Xcode 16 is locate here

 

Edited October 3, 2025 by chris1111

[MakAsrock]

3 hours ago, Stefanalmare said:

I had this error in Sequoia with Xcode 26.0.1.

Question for the author of Builder.sh Here are the compilation results on GitHub.
 

Edited October 3, 2025 by MakAsrock

[chris1111]

5 hours ago, Max.1974 said:

With buildme directly, compile with python 3.13.5, same warning appears. 

 

 

I will show my compiler Builder in Ventura soon 

 

 

Thanks @Max.1974 take a look here

the culprit is Xcode 26

 

[MakAsrock]

45 minutes ago, chris1111 said:

Thanks @Max.1974 take a look here

the culprit is Xcode 26

 

Please pay attention to dependency: Tahoe Xcode 26.1 requires Python 3.13.7, not 3.13.5, and not 3.13.6. I managed to use a borrowed iPhone to connect Tahu to the Router and, as always, everything is fine without errors or warnings. I used the command line tools that came with Xcode 26.1 (xcode-select version 2410) and Python 3.13.7 Well, I don’t have a network outlet in my apartment.

Edited October 3, 2025 by MakAsrock

[MakAsrock]

There are no problems with the command line tool 26.01 and I don't have any others!!!

Hi friends and respected author of Clover Builder v14 Tahoe version,

I wanted to provide some feedback regarding the current buildme script on macOS Tahoe:

1. The current buildme does not support Xcode versions below 16.x and Python versions below 3.13.7.

2. It strongly conflicts with Homebrew. Homebrew changes system paths, which buildme does not expect. The script looks for toolchain binaries only inside its own repository or two levels above in /opt/bin, ignoring Homebrew locations.

3. I was able to reproduce the issue on Tahoe, but simply removing Homebrew and reinstalling Xcode and Python was not sufficient to fix it. The only way I managed to eliminate the errors was by reinstalling macOS 26.1.

These restrictions make the current buildme quite rigid regarding environment setup.

I would be happy if I could adapt buildme to make it work more flexibly in different environments.

Best regards, Yitzhak Bronstein.

Edited October 3, 2025 by MakAsrock

[Max.1974]

6 hours ago, chris1111 said:

Thanks @Max.1974 take a look here

the culprit is Xcode 26

 

 

Thanks @chris1111 my friend, you are absolutely right, using Xcode 16.4 everething compile without warnings! Thanks a lot !! 

 

https://download.developer.apple.com/Developer_Tools/Xcode_16.4/Xcode_16.4.xip

 

 

 

 

 

 

@MakAsrock using basic python like Slice said on AppleLifeRu working fine too my friend. Thanks for your hard work too!! 

[Max.1974]

4 hours ago, MakAsrock said:

There are no problems with the command line tool 26.01 and I don't have any others!!!

Hi friends and respected author of Clover Builder v14 Tahoe version,

I wanted to provide some feedback regarding the current buildme script on macOS Tahoe:

1. The current buildme does not support Xcode versions below 16.x and Python versions below 3.13.7.

2. It strongly conflicts with Homebrew. Homebrew changes system paths, which buildme does not expect. The script looks for toolchain binaries only inside its own repository or two levels above in /opt/bin, ignoring Homebrew locations.

3. I was able to reproduce the issue on Tahoe, but simply removing Homebrew and reinstalling Xcode and Python was not sufficient to fix it. The only way I managed to eliminate the errors was by reinstalling macOS 26.1.

These restrictions make the current buildme quite rigid regarding environment setup.

I would be happy if I could adapt buildme to make it work more flexibly in different environments.

Best regards, Yitzhak Bronstein.

 

 

Thanks my friend, I will make tests as possible and report feedback here!! Thanks!! 

[miliuco]

@chris1111

 

OT. If I understand you well, can Xcode 16.4 be installed on Tahoe? The normal installer? Thanks. 

 

 

 

[chris1111]

4 hours ago, miliuco said:

@chris1111

 

OT. If I understand you well, can Xcode 16.4 be installed on Tahoe? The normal installer? Thanks. 

 

 

 

Yes you can use both Xcode

Xcode 26 and Xcode 16

see my images

Edited October 3, 2025 by chris1111

[LockDown]

@Slice Sequoia & Tahoe is supported with this feature?

Update: it works👍

Edited October 4, 2025 by LockDown

[chris1111]

To All Build Clover on macOS Tahoe 26 from scratch 

This instructions will build Clover without external build script

✌️

[Max.1974]

Hi @chris1111 

 

Hello my dear friend, the Clover Builder was designed to update Python and also reuse binaries, avoiding the time-consuming process of downloading and reconfiguring GCC. But thank God the Git from Clover was updated — that makes things much easier for everyone. I’d like to emphasize that the tool doesn’t change the essence of Clover; it simply gives us options to update, refresh, or re-clone the Clover folder from scratch, and helps prevent common errors that occur with each Xcode or macOS change. Thank you for keeping Clover up to date. Everything compiled perfectly here.

 

 

 

 

 

Edited October 4, 2025 by Max.1974

[Max.1974]

I will still using my compiler because re auto-saved to src-binaries  but I deleted post from Hackintosh Tools for people using directly from git clover