From: "nobu (Nobuyoshi Nakada)" Date: 2013-02-13T09:45:57+09:00 Subject: [ruby-core:52171] [ruby-trunk - Bug #7830] Ruby packages should not build with -Werror when distributed Issue #7830 has been updated by nobu (Nobuyoshi Nakada). kosaki (Motohiro KOSAKI) wrote: > No. -Werror-implicit-function-declaration also make compilation error > when compiler make new code analysis. Why do you think so? Of course it is same. Unfortunately apple-gcc still doesn't make an implicit function declaration error by -Werror= option, even if sole -Werror. ---------------------------------------- Bug #7830: Ruby packages should not build with -Werror when distributed https://bugs.ruby-lang.org/issues/7830#change-36186 Author: kremenek (Ted Kremenek) Status: Open Priority: Normal Assignee: Category: Target version: ruby -v: N/A I represent the Clang compiler team at Apple, and I've heard some complaints that Clang does not work well for building Ruby. Clearly we care that Clang can compile the Ruby sources. The complaints seemed to have varied over time, but the most recent one that was reported to me seems captured by the following discussion: https://github.com/plamoni/SiriProxy/issues/436 Here the problem is that a warning is being promoted to an error via -Werror. While -Werror is a great development tool, it is not a great mechanism to enable for distributing packages as sources. Different compilers, and different versions of the same compiler, may issue different warnings, and using -Werror in source packages makes those packages very brittle to new compiler changes. With Xcode releases, we frequently enable new (or existing) warnings by default that have shown to be quite useful to finding problems. Those new warnings typically are great for development, but when coupled with -Werror and packaged sources (that aren't really changing) they can be disastrous. I do not actively build Ruby myself, but I request that Ruby software packages should not be distributed with -Werror enabled. This will greatly help users installing Ruby via homebrew or macports, and this likely will be an issue on other platforms besides OS X as well. -- http://bugs.ruby-lang.org/