-
-
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
xerces-c 3.2.0 #17371
xerces-c 3.2.0 #17371
Conversation
Formula/xalan-c.rb
Outdated
@@ -25,6 +26,7 @@ class XalanC < Formula | |||
|
|||
def install | |||
ENV.deparallelize # See https://issues.apache.org/jira/browse/XALANC-696 | |||
ENV["CXXFLAGS"] = "-std=c++11" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You'll want to use
needs :cxx11
and
ENV.cxx11
instead.
Formula/xalan-c.rb
Outdated
ENV.deparallelize # See https://issues.apache.org/jira/browse/XALANC-696 | ||
ENV["CXXFLAGS"] = "-std=c++11" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this shouldn't be needed now that you've added ENV.cxx11.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
D'oh. I'll push that in just a second.
@ilovezfs I've updated the revision of the dependent packages and added C++11 support there, but it's not building them in the CI testing AFAICT. Is something else missing? The errors when testing the bottled version are because the soname changed. |
@rleigh-codelibre the ones that are failing need to be revision bumped. |
@rleigh-codelibre I have pushed the revision bumps. |
@ilovezfs Thanks. Some of them might need C++11 enabling. And some like zquilla need some patches to fix incompatibilities in the code. I'm working my way through these in the BSD ports tree, and I'll carry the patches over to homebrew once I've tested them. |
@ilovezfs I've patched all the necessary packages and filed bug reports upstream wherever possible. The remaining errors are not in this PR but are warnings about existing problems:
Should these problems be addressed in this PR? I'm not exactly sure what the fixes are for these audit violations. |
Nope. They're being tracked in #13133.
Please submit PR(s) to https://github.com/Homebrew/formula-patches so they don't have to live in the formulae themselves. |
@ilovezfs I've opened Homebrew/formula-patches#175 . I'll update this PR once that one is merged? |
@rleigh-codelibre I've merged all the patches, and I apologize for pinging you repeatedly whilst doing so. However, you should be set to move this PR forward. Thank you for your patience. |
@rleigh-codelibre ping. Also note that this PR should be 1 commit per formula. |
Thanks. I'm away for the next week, so I'll update this in 8 days. |
@BrewTestBot test this please |
1 similar comment
@BrewTestBot test this please |
Looks like this needs to be rebased. |
Right. But rleigh-codelibre is away for a few days, so … |
There's one audit failure which seems to be in shibboleth-sp related to curl/openssl, unrelated to this PR. |
@BrewTestBot test this please |
@gvenzl do you have any idea who we should report the patch for dbxml to? (see https://raw.githubusercontent.com/Homebrew/formula-patches/master/dbxml/c%2B%2B11.patch) |
@BrewTestBot test this please |
1 similar comment
@BrewTestBot test this please |
Thanks @rleigh-codelibre! You're awesome :) ❇️ 🎉 🎊 |
brew install --build-from-source <formula>
, where<formula>
is the name of the formula you're submitting?brew audit --strict <formula>
(after doingbrew install <formula>
)?Note, this release switches to cmake, and this automatically enables the use of
char16_t
for unicode strings in place ofuint16_t
. This means you can useu"string"
directly which is a nice usability gain, but it does mean that all packages using xerces-c must compile with C++11 enabled. If this proves to be a problem, we can explicitly disable it until Xcode enables it by default. I've patched xalan-c (https://issues.apache.org/jira/browse/XALANC-773).