[haiku-commits] Re: haiku: hrev46660 - build/jam src/system/libroot/posix/glibc/stdio-common
- From: Jonathan Schleifer <js-haiku-commits@xxxxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Thu, 16 Jan 2014 17:20:52 +0100
Am 16.01.2014 um 17:13 schrieb Stephan Aßmus <superstippi@xxxxxx>:
> On 16.01.2014 16:53, Jonathan Schleifer wrote:
>> * If you allow to use any installed Clang, it means you will also test Haiku
>> with Clang from trunk and thus *if* there is a problem realize it early
>> enough to fix it → we can make sure a Clang release never breaks for Haiku,
>> meaning a new Clang release will *never* break, completely eliminating the
>> need to require a specific version. Therefore version x.y or up will be fine
>> and there's no need to always build a bundled Clang.
>
> Actually, the user who is trying to compile Haiku on his system will notice
> it. He or she will probably be frustrated.
That is what I said about enabling -Wall -Werror. But there it was ok because
it reveals bugs. And now it's suddenly not ok for another even though it
reveals? Sounds like double standards to me…
--
Jonathan
Other related posts:
