From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8170 invoked by alias); 27 Jan 2012 20:15:26 -0000 Received: (qmail 8149 invoked by uid 22791); 27 Jan 2012 20:15:21 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-gx0-f169.google.com (HELO mail-gx0-f169.google.com) (209.85.161.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 27 Jan 2012 20:15:00 +0000 Received: by ggnr5 with SMTP id r5so473766ggn.0 for ; Fri, 27 Jan 2012 12:15:00 -0800 (PST) Received: by 10.50.156.196 with SMTP id wg4mr7902576igb.13.1327695300161; Fri, 27 Jan 2012 12:15:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.231.15.71 with HTTP; Fri, 27 Jan 2012 12:14:40 -0800 (PST) In-Reply-To: <630818d4-a076-4ecd-a42d-7ede597769b8@zose-store-12> References: <630818d4-a076-4ecd-a42d-7ede597769b8@zose-store-12> From: Chris Morgan Date: Fri, 27 Jan 2012 20:15:00 -0000 Message-ID: Subject: Re: CLooG build error To: =?ISO-8859-1?Q?Beno=EEt_Th=E9baudeau?= Cc: Johannes Stezenbach , crossgcc@sourceware.org, "Yann E. MORIN" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org X-SW-Source: 2012-01/txt/msg00080.txt.bz2 2012/1/27 Beno=EEt Th=E9baudeau : > Chris, > >> Oddly I only have 0.15.10 or older in my list of CLooG versions. >> Maybe >> because I'm targetting arm or some other option that is affecting the >> available versions on the list? > > It's because 0.15.11 appears in the config options only if the > experimental features are enabled in the config. > > Beno=EEt Oh ok. Let me enable that and use 0.15.11 and retry. I retried after your patch and it failed, then noticed that I was using 0.15.10. Chris -- For unsubscribe information see http://sourceware.org/lists.html#faq