X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding :in-reply-to; q=dns; s=default; b=HEvIiL9+j9PNkgHOzS6GXFQrtyT0le IX8O3kfnyIZHZtlbl5W8u4PCp5/tk+yVmOfnoSG/ZypjYhHgURhHHT+e3lv+DEtx G/T4WCuLkq32FXbH35wtt6ZuiK0CN4b82qAkHo5KM+lEEILCALJst8ZYb/n8kMcX vUE9zo0QDef/4= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding :in-reply-to; s=default; bh=yBPFYFClTK58uEbzZ0J6tjzi95g=; b=BXtl pvcoeio1tj9ShzMT5gYyhq6DS+P8IcLOJ3ZEeflGn9P8yaZqwz/caimy7RbV75IV lxngzSY9AuC+Xm5f4yfWl4vnkDvYjauxiqo27Drn/XvLGE/ehilSX8HBMjlWHoCE 0XToi9ptRsqu+WIuBvjQrWA5WFrfQlq0xWIugxg= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=-0.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,FSL_HELO_BARE_IP_2,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.1 To: cygwin AT cygwin DOT com From: jojelino Subject: Re: clang++ broken by recent GCC update Date: Sat, 06 Jul 2013 00:29:42 +0900 Lines: 8 Message-ID: <51D6E666.20102@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:24.0) Gecko/20100101 Thunderbird/24.0a1 In-Reply-To: On 2013-07-04 PM 9:47, Václav Zeman wrote:> Hi. > > The C++ part of Clang package (I have not tested the C part) is broken > after update of GCC to 4.7.3. It cannot find standard C++ headers: > > Clang does use hard-coded include path for using gcc header files. Please build your own or you can file bug report to clang. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple