You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains 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
if do_vcs "https://github.com/xiph/opusfile.git";then
do_uninstall "${_check[@]}"
do_patch "https://gist.githubusercontent.com/1480c1/c3f32033ad4a07264e2063f0fb38fc1b/raw/0001-Disable-cert-store-integration-if-OPENSSL_VERSION_NU.patch" am
do_patch "https://gist.githubusercontent.com/1480c1/beb86dbd8f79e3c1e06d6e9053804f52/raw/0001-Disable-cert-store-integration-if-OPENSSL_VERSION_NU.patch" am
do_patch "https://gist.githubusercontent.com/1480c1/beb86dbd8f79e3c1e06d6e9053804f52/raw/0002-configure-Only-add-std-c89-if-not-mingw-because-of-c.patch" am
The reason will be displayed to describe this comment to others. Learn more.
I can try proposing the c89 one since technically inline in c89 is a gnu extension, the other one is lifted off a comment from @lazka from xiph/opusfile#13 so that one will rely on if he wants to
The reason will be displayed to describe this comment to others. Learn more.
Rather, the inline part is actually caused by mingw-w64's headers having inline in them, so I'm not sure how much of this is because of opusfile or actually just clang's issue
The reason will be displayed to describe this comment to others. Learn more.
So the wincert one is because we still have libressl (which is still on a lower OpenSSL version), so it's kind of specific to the combination of opusfile+libressl.
And the other one you're not sure if it's an issue with opusfile's usage of inline or with mingw's usage of inline. So compiling with MinGW means c89 should not be used?
0091924
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.
Did you try proposing these patches to upstream?
0091924
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.
I can try proposing the c89 one since technically
inline
in c89 is a gnu extension, the other one is lifted off a comment from @lazka from xiph/opusfile#13 so that one will rely on if he wants to0091924
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.
Rather, the inline part is actually caused by mingw-w64's headers having inline in them, so I'm not sure how much of this is because of opusfile or actually just clang's issue
0091924
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.
So the wincert one is because we still have libressl (which is still on a lower OpenSSL version), so it's kind of specific to the combination of opusfile+libressl.
And the other one you're not sure if it's an issue with opusfile's usage of
inline
or with mingw's usage ofinline
. So compiling with MinGW means c89 should not be used?Yeah, it's muddy.