Doctor: "Warning: No Cask quarantine support available: unknown reason" #5482
Replies: 12 comments 22 replies
-
|
Your |
Beta Was this translation helpful? Give feedback.
-
I got the same issue when I upgraded to macOS 15.0, The output of the above command is: my brew config: |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
I have the same issue. Thankfully, I run this <unknown>:0: error: PCH was compiled with module cache path '/var/folders/14/07yvz9pj24s2r70gt87n3k2r0000gn/C/org.llvm.clang.zorn/ModuleCache/2ZDVRZCAEUI7H', but the path is currently '/var/folders/14/07yvz9pj24s2r70gt87n3k2r0000gn/C/org.llvm.clang.Zorn/ModuleCache/2ZDVRZCAEUI7H'
<unknown>:0: error: missing required module 'SwiftShims'Then I just delete the cache folder |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure if it is relevant, and I'm not totally sure how to test it really, but I also see this error message:
My only suspicion is that I am running the latest MacOS on a legacy Mac, via OpenCore which I think has implications on the strictness of SIP. Maybe that is part of the reason? |
Beta Was this translation helpful? Give feedback.
-
|
Our situation is similar. I am using the hackintosh drived by opencore and opencore-patcher. You can try the command |
Beta Was this translation helpful? Give feedback.
-
|
Oh wild, that one for me gives me And that appears to be a private API internal to Homebrew? It says I am up to date though 🥴 Attempted to reinstall Homebrew with the package and didn't seem to take much effect 🤔 |
Beta Was this translation helpful? Give feedback.
-
|
same error with me |
Beta Was this translation helpful? Give feedback.
-
|
Swift (including the |
Beta Was this translation helpful? Give feedback.
-
|
I attempted a full reinstall of Xcode, that otherwise seems to be running fine and my |
Beta Was this translation helpful? Give feedback.
-
|
Same issue on a brand new re-install of macOS 14.7 M3 Brew doctor:Brew config: |
Beta Was this translation helpful? Give feedback.
-
|
The common factor here in the reports from the last few days appears to be people have CLT 15.3 installed but have the macOS 15 SDK. This should be impossible as only CLT 16.0 contains the macOS 15 SDK. It sounds like something (potentially a bug in |
Beta Was this translation helpful? Give feedback.
-
|
Same issue on macOS 14.6. I only have command line tools installed - not Xcode.
|
Beta Was this translation helpful? Give feedback.
-
|
Same issue after updating macOS to Sonoma 14.7, only I do have Xcode (version 16) installed.
|
Beta Was this translation helpful? Give feedback.
-
|
some problem on sequoia with opencore but all its ok on brew... why this message? |
Beta Was this translation helpful? Give feedback.
-
|
Because some features will not work. |
Beta Was this translation helpful? Give feedback.
-
|
Did some testing on my end and it seems that something probably changed in Sequoia with the Driver file (everything save the first import Foundation
struct SwiftErr: TextOutputStream {
public static var stream = SwiftErr()
mutating func write(_ string: String) {
fputs(string, stderr)
}
}
print(CommandLine.arguments)
var dataLocationURL = URL(fileURLWithPath: CommandLine.arguments[1])
do {
let isDataLocationURLReachable = try dataLocationURL.checkResourceIsReachable()
} catch {
print(error.localizedDescription, to: &SwiftErr.stream)
exit(1)
}
Seems to me that changing I have a normal Monterey installation that I can try stuff on if necessary. |
Beta Was this translation helpful? Give feedback.
-
|
Intriguing... Just checked that the latest CLT from Monterey works as intended with both the driver file (reads one argument and exits because
But the stack dump reports the full call list like Sequoia does...
Just in case, MacBook Pro 12,1, Sequoia is with OCLP, Monterey is natively booted. |
Beta Was this translation helpful? Give feedback.
-
|
It seems that this one liner is enough to demonstrate the problem. Curiously it behaves normally if invoked over print(CommandLine.arguments) |
Beta Was this translation helpful? Give feedback.
-
|
Have you tested it again with Swift 6.0.2 released today in CLT 16.1? |
Beta Was this translation helpful? Give feedback.
-
|
Yes.
|
Beta Was this translation helpful? Give feedback.
-
|
Same issue I re-run it a second time and it succeeds. No idea how to fix yet, maybe homebrew will find a fix eventually. |
Beta Was this translation helpful? Give feedback.
-
|
After a clean install of macOS 14.17.1 (Sonoma) and the latest CLT, I am still seeing the warning as well. |
Beta Was this translation helpful? Give feedback.
-
|
Do you use opencore patcher? |
Beta Was this translation helpful? Give feedback.
-
|
No, just a straight re-install directly from Disk Utilities |
Beta Was this translation helpful? Give feedback.
-
|
Same problem for me, brand new sequoia 15.1 reinstall on an elegible intel macbook air.
After switching xcode-select to Xcode 16.1.0 (installed via xcodes), both the warning and the subsequent swift check error are solved. |
Beta Was this translation helpful? Give feedback.
-
I download lastest command line tools, doesn't work, I try xcode later. |
Beta Was this translation helpful? Give feedback.
-
i install xcode 16.1.0 with app store, it doesn't work, |
Beta Was this translation helpful? Give feedback.
-
Output of
brew configOutput of
brew doctorDescription of issue
The command
brew doctorsays:I haven't been able to find any relevant information on how to resolve this issue (Google returns like 5 irrelevant results). Because I need an empty output of the doctor command to create a new issue in the Brew repository, it's blocking me from creating new issues. And I just need to create one.
Is anyone able to help me with this issue, please?
Beta Was this translation helpful? Give feedback.
All reactions