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
[PATCH] 126c780 cflags: clang complains a lot about -Wunused-value which are not fixable #12150
Comments
From @rurbanThis is a bug report for perl from rurban@cpanel.net, From 126c78033897e8672291fa097930f63931922102 Mon Sep 17 00:00:00 2001 cflags.SH | 4 ++++ Inline Patchdiff --git a/cflags.SH b/cflags.SH
index f57cf2f..ac03b85 100755
--- a/cflags.SH
+++ b/cflags.SH
@@ -337,6 +337,10 @@ for file do
cppflags=`echo $cppflags|sed 's/-Wdeclaration-after-statement/ /'`
case "$cc" in
+ *clang)
+ # clang complains a lot about -Wunused-value which are not fixable
+ warn="$warn -Wno-unused-value"
+ ;;
*g++*)
# Without -Wno-unused-variable g++ 4.x compiles are rather unwatchable
# because of all the warnings about Perl___notused, and g++ doesn't do
--
Flags: Site configuration information for perl 5.17.0: Configured by rurban at Tue May 29 09:27:49 CDT 2012. Summary of my perl5 (revision 5 version 17 subversion 0) configuration: Locally applied patches: @INC for perl 5.17.0: Environment for perl 5.17.0: |
From @tonycozOn Thu, May 31, 2012 at 01:00:48PM -0700, rurban@cpanel.net (via RT) wrote:
Not fixable in that we can't fix perl? or that clang can't be fixed? Tony |
The RT System itself - Status changed from 'new' to 'open' |
From @khwilliamsonOn 06/03/2012 07:56 PM, Tony Cook wrote:
I have tried to figure out a way to silence some of these warnings by |
From @rurbanThat we cannot fix perl, without making it worse. |
From @cpansproutOn Thu May 31 13:00:48 2012, rurban@cpanel.net wrote:
Thank you. Applied as d5db65c. -- Father Chrysostomos |
@cpansprout - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#113450 (status was 'resolved')
Searchable as RT113450$
The text was updated successfully, but these errors were encountered: