-
-
Notifications
You must be signed in to change notification settings - Fork 12.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Top Big Sur bottling issues #65000
Comments
Regarding [email protected], this is mainly an Xcode 12 compatibility problem. @SMillerDev has worked on this, see #61828. Given that php 7.2 will be EOL in less than two weeks, I wonder if it's worth patching the package, though. |
Just remove it already IYAM. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
* groff: fix build See #65000 (comment) Builds on #64842 - [x] Have you followed the [guidelines for contributing](https://github.com/Homebrew/homebrew-core/blob/HEAD/CONTRIBUTING.md)? - [x] Have you checked that there aren't other open [pull requests](https://github.com/Homebrew/homebrew-core/pulls) for the same formula update/change? - [x] Have you built your formula locally with `brew install --build-from-source <formula>`, where `<formula>` is the name of the formula you're submitting? - [x] Is your test running fine `brew test <formula>`, where `<formula>` is the name of the formula you're submitting? - [x] Does your build pass `brew audit --strict <formula>` (after doing `brew install <formula>`)? Newly added dependencies are for creating PDF and HTML files, and for recognising file encoding. * Update groff.rb * Update groff.rb Closes #65042. Co-authored-by: Jonathan Chang <[email protected]> Signed-off-by: Jonathan Chang <[email protected]> Signed-off-by: BrewTestBot <[email protected]>
Regarding tarantool.The build fails with the following error:
Is it the build environment problem or something on our side? |
It might need to depend on |
This comment has been minimized.
This comment has been minimized.
|
I've got pypy seeming to build locally and have opened #65854 to see if it'll bottle. |
I opened a PR that should fix |
Over the last couple days I took a look through some of the formula in @jonchang's "Big list" above... either packages I have some past familiarity with or things that just looked interesting: Fixed and already merged:
PRs open but not merged yet:
Nominated for removal:
Builds fine for me, not sure what the bottling problem was:
Unchecked things in @jonchang's "Big list" that seem to have already been resolved (Big Sur bottles currently exist):
|
A word of caution about perl-based formula -- I've been having a hell of a time with them. First there is the issue where MakeMaker seems to have changed how it lays out the directory by default. I've seen that a couple times already, and have what I think is a workaround even though I don't understand the underlying problem (e.g. #66367 and #66370) Today I took what I thought would be a quick look at At the root, this is the same type of issue as things like #66304 where the build scripts assume they can probe for the Basically, if you see a broken formula that relies on MakeMaker be afraid. |
Hit a few more. Fixed and already merged:
PRs open but not merged yet:
Investigated:
Builds fine for me, not sure what the bottling problem was:
Also have leads on some other root causes that might affect multiple formulae:
|
I've updated the list at the top. I've also started bottling jobs for:
|
|
I was afraid you were going to say that :-/ |
When looking at Homebrew packages that no longer build correctly ( Homebrew/homebrew-core#65000 ) I decided to take a quick look at mogenerator although I didn't know anything about the package before. The build failure at first seemed very odd. The final link was failing with: error: Build input file cannot be found: '[...]/objroot/mogenerator.build/Release/mogenerator.build/DerivedSources/mogenerator-Info.plist' [...] At first I assumed that the build-mogenerator-Info-plist.sh script either did not run or failed to produce the expected file. However, after adding some more debugging statements that does not seem to be the case. The script definiely runs and you can see the output from PlistBuddy in the build output: Unrecognized Type: File Doesn't Exist, Will Create: /tmp/mogenerator-20201222-40012-136lzn9/mogenerator-1.32/objroot/mogenerator.build/Release/mogenerator.build/DerivedSources/mogenerator-Info.plist Initializing Plist... (The first message comes from the use of the '-c "Clear"' line since "Clear" is supposed to take an argument I guess.. however that seems unrelated to the build failure) Digging more into the .pbxproj file I noticed that the "outputPaths" from the build-mogenerator-Info-plist.sh build step seems to be wrong... perhaps just a typo. I fixed that and the build worked. My theory is that since xcodebuild wasn't seeing the proper dependency graph it maybe started the link before the plist was finished being written out? Anyway it looks like the outputPaths were wrong and repairing that made this package build again for me. YMMV.
elm already has a bottle #67404 |
✅ haskell-stack bottled: #67809 |
When I last put my copy of the list on this thread 15 days ago ( #65000 (comment) ) it had 281 enties. Now we're down to 165 remaining by my count... so definitely good progress. Here are my current notes; let me know if you have updates:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
PR for |
|
The list is for Intel Big Sur, not ARM. |
It's been awhile since I posted the current version of my list. The last one had 165 lines, now we're down to just 75!
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
We already have a massive issue that's systematically tracking and collating all Big Sur bottling failures: #64785 In this issue, I want to track a prioritised list of failures among our top-downloaded formulas, so we track progress and participation.
This top post will be edited over time to remain accurate. Discussion and offers of help can go below.
List of formulas missing a Big Sur bottle (and number of montly installs):
The text was updated successfully, but these errors were encountered: