From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2777 invoked by alias); 31 Jul 2009 17:52:55 -0000 Received: (qmail 2765 invoked by uid 22791); 31 Jul 2009 17:52:55 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_42,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx2.redhat.com (HELO mx2.redhat.com) (66.187.237.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 31 Jul 2009 17:52:46 +0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n6VHqDVT006231; Fri, 31 Jul 2009 13:52:23 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n6VHq7mu003652; Fri, 31 Jul 2009 13:52:07 -0400 Received: from opsy.redhat.com (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n6VHq6bG008784; Fri, 31 Jul 2009 13:52:06 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id DB8933782DC; Fri, 31 Jul 2009 11:52:05 -0600 (MDT) To: Basile STARYNKEVITCH Cc: GCC Mailing List Subject: Re: MELT tutorial on the wiki References: <4A707003.8060103@starynkevitch.net> <4A728EE2.2050401@starynkevitch.net> From: Tom Tromey Reply-To: tromey@redhat.com Date: Fri, 31 Jul 2009 17:52:00 -0000 In-Reply-To: <4A728EE2.2050401@starynkevitch.net> (Basile STARYNKEVITCH's message of "Fri\, 31 Jul 2009 08\:27\:46 +0200") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-07/txt/msg00638.txt.bz2 >>>>> "Basile" == Basile STARYNKEVITCH writes: Basile> My current belief is that MELT is easier built (and used) as a Basile> GCC-trunk (or future GCC-4.5) plugin melt.so. Yeah, I looked at this, but I really wanted something where I did not have to do much work... no applying patches or hacking scripts. I have very little time for this side project, so most barriers look too big at this point. Tom> In both cases I just configured with --disable-bootstrap --enable-melt, Tom> plus the appropriate --enable-langauges option. This is on x86 F11. Basile> You probably missed some configure arguments. The MELT's Basile> gcc/configure.ac ends with Basile> ## Basile adds a notice if the MELT branch is configured without Basile> ## --enable-melt Basile> if test "$enabled_melt" != "yes" ; then Basile> AC_MSG_NOTICE( Basile> [GCC MELT branch is configured WITHOUT enabling melt. Basile> Are you sure to want that?]) Basile> fi I looked into this a little. It looks like the PPL checks don't work properly in the case where PPL is a system library. I guess I need --with-ppl=/usr ... I will try that later. BTW: IMO, on a branch like this, it would be friendlier for users to: * Check in the correct version of configure * Enable MELT by default, don't require an option * Die in configure if a prerequisite is missing * Have the PPL checks detect the situation where PPL is a system library Otherwise whatever error messages there might be are just lost in the noise. Tom