Skip to content
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

fix: update parser header file with namespaced functions #364

Conversation

jamescdavis
Copy link
Contributor

@jamescdavis jamescdavis commented Jul 29, 2020

d5b523e renamed the parser functions to include a thin_ prefix as a namespace, but did not update the parser header file. This did not cause any problems for a long time because implicit-function-declaration was just a warning previously, but Xcode 12 has made it an error (second bullet under Apple Clang Compiler > Resolved):

Clang now reports an error when you use a function without an explicit declaration when building C or Objective-C code for macOS (-Werror=implicit-function-declaration flag is on). This additional error detection unifies Clang’s behavior for iOS/tvOS and macOS 64-bit targets for this diagnostic. (49917738)

This is preventing install of this gem on macOS with Xcode 12.

Note: there is a workaround until this is patched:

$ gem install thin -- --with-cflags="-Wno-error=implicit-function-declaration"

or with Bundler:

$ bundle config build.thin --with-cflags="-Wno-error=implicit-function-declaration"

@danzanzini
Copy link

I couldn't install another gem that has thin as a dependency because of this error. Thank you for this PR and for the workaround.

It solved the problem.

@stanhu
Copy link

stanhu commented Aug 21, 2020

Thanks for the pull request! Could someone tag a new release please? Has it really been 3 years? :) https://rubygems.org/gems/thin/versions/1.7.2

@jamescdavis jamescdavis deleted the update_parser_header_file_with_namespaced_functions branch August 21, 2020 02:40
@ioquatix
Copy link
Collaborator

ioquatix commented Sep 7, 2020

Yes we will do a new release soon, it will probably be 1.8.0.

@ioquatix ioquatix added this to the v1.8.0 milestone Sep 7, 2020
@stanhu
Copy link

stanhu commented Sep 28, 2020

@ioquatix Thank you. Friendly reminder: would you mind releasing a new version? With XCode v12 becoming the default, a number of people are hitting this error.

@wagenet
Copy link

wagenet commented Nov 10, 2020

@ioquatix any update on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants