From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25157 invoked by alias); 13 Sep 2015 23:19:40 -0000 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 Received: (qmail 25147 invoked by uid 89); 13 Sep 2015 23:19:39 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mail.anw.at Received: from ns1.anw.at (HELO mail.anw.at) (195.234.101.234) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Sun, 13 Sep 2015 23:19:38 +0000 Received: from [10.12.40.38] ([195.29.66.214]) by mail.anw.at (8.14.4/8.14.4/Debian-4) with ESMTP id t8DNJZdW029291 for ; Mon, 14 Sep 2015 01:19:35 +0200 Message-ID: <55F60487.5030805@anw.at> Date: Sun, 13 Sep 2015 23:19:00 -0000 From: "Jasmin J." User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: crossgcc@sourceware.org Subject: Re: [RFC] Refactor autoconf options and build scripts References: <20150912200305.69b80a14@free-electrons.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2015-09/txt/msg00034.txt.bz2 Bryan, > Yann has given > me access to one he uses for building, and I need to get time to sit > down and get some build tests going, for at least the samples/ > directory. If we use travis-ci, we would gain a good integration to GitHub. You can check any pull request before you add it into master automatically. > I would also hope in that testing that I might be able to expose and > to utilize a randconfig for ct-ng. This would help to build random > configs and find combinations of options that should have constraints. This might be something for Yann's server. >> For >> example, Crosstool-NG does not ensure that the proper cloog/mpc/gmp >> version is selected for a given version of gcc (solution: make the >> version of those components not configurable). > > With current master, I know this to be true. I need to be more strict with PRs. The problem are the lacking predefined configurations, which are known to work. Then each contributor can easily check if a patch doesn't break any of this combinations. For me, as a newbee to CT-NG, it is nearly impossible to know working combinations. So the solution to this problem is regression testing, no matter if it is done manually or automatic by Jenkins, Buildbot or travis-ci. BR Jasmin -- For unsubscribe information see http://sourceware.org/lists.html#faq