Allow build time --with-cflags option to work #123
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The current extconfg.rb overwrites $CFLAGS variable breaking usual gem -- --with-cflags="..." way of setting it
Fix build, added cflags need padding
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current extconfg.rb overwrites
$CFLAGSvariable breaking usualgem install zstd-ruby -- --with-cflags="..."way of setting itI ran into this when trying to compile the gem with musl on arm64 where a
PATH_MAXconstant is not set, and couldn't getgemcommand to add it to the generated makefile with--with-cflagsAs a workaround
--with-cppflags="..."works because that is already with+=in extconf, but i see no reason why break normal cflags