-
Notifications
You must be signed in to change notification settings - Fork 0
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
[pull] master from sparklemotion:master #4
base: master
Are you sure you want to change the base?
Conversation
Hey! Changelogs info seems to be missing or might be in incorrect format. |
- extract helper concat_flags - strip spaces from configuration params
and skip printing the big notice if the library is already build
if, for example, CFLAGS appeared multiple times then it would get clobbered. this change appends all the values to a single set of flags.
This is the default for those libraries, but we were overriding CFLAGS in some cases. Additionally, we need to compile with -U_FORTIFY_SOURCE to avoid Ubuntu's convention of setting -D_FORTIFY_SOURCE=2 when -O2 is set. This leads to problems when running precompiled libraries on musl (see #2100 for details). Closes #2022.
…rintf-and-some-warnings clean up vasprintf and some warnings, and clean up extconf.rb
Nokogiri always have had dependency on Racc, but it was never stated explicitly. This is possible issue for several reasons: 1) There is no way RubyGems/Bundler could avoid loading wrong version of Racc if other package in application specifies different version of Racc then Nokogiri needs. 2) If there is released incompatible Racc 2.x, all old versions of Nokogiri will be broken just because it does not specify its dependencies properly. 3) If Ruby decides to drop Racc from StdLib, all Nokogiri versions will be broken (unnoticeably). Or Ruby will be forced to carry Racc around around although it is possibly obsolete. Fixes #1988
Add explicit Racc depenency.
…ned-by-glibc fix: avoid collision with glibc's canonicalize() method
Fix typo in comment
based on inspection of the pkg_config gem. also: - extract pkg_config gem version requirement - improve the explanatory comment
also remove unnecessary spaces in some CPPFLAGS
to clarify that the presence of the env variable turns the switch on, and the value is ignored
This was set before discovering the encoding problem was with iconv support (see eb69384)
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 fixed the issue(s)! Great work.
ci: switch to the ruby/setup-ruby action
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 fixed the issue(s)! Great work.
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 fixed the issue(s)! Great work.
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.
There are accessibility issues in these changes.
@@ -1,21 +1,27 @@ | |||
<div><img src="https://nokogiri.org/images/nokogiri-serif-black.png" align="right"/></div> |
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 image is missing a text alternative (alt
attribute). This is a problem for people using screen readers.
Updates the requirements on [rubocop](https://github.com/rubocop-hq/rubocop) to permit the latest version. - [Release notes](https://github.com/rubocop-hq/rubocop/releases) - [Changelog](https://github.com/rubocop-hq/rubocop/blob/master/CHANGELOG.md) - [Commits](rubocop/rubocop@v0.88.0...v1.7.0) Signed-off-by: dependabot[bot] <[email protected]>
…p-tw-1.7 build(deps-dev): update rubocop requirement from ~> 0.88 to ~> 1.7
to include a question about native gems
to check that we're setting error handlers everywhere we need to. Related to #2168
originally introduced in 771164d but broken in the recent commits. This is an incomplete fix. We should adopt this same strategy of save-and-restore everywhere we set the error handlers.
…failure fix(cruby): SAX and Push parser error handling in the presence of foreign handlers
removing stale entries and grouping
to be clear that --with-foo-lib and --with-foo-include can be passed for any of the libraries.
See Commits and Changes for more details.
Created by pull[bot]. Want to support this open source service? Please star it : )