From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10652 invoked by alias); 13 Sep 2015 22:59:52 -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 10642 invoked by uid 89); 13 Sep 2015 22:59:52 -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 22:59:50 +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 t8DMxkHb021944 for ; Mon, 14 Sep 2015 00:59:46 +0200 Message-ID: <55F5FFE2.5010505@anw.at> Date: Sun, 13 Sep 2015 22:59: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: <20150912200305.69b80a14@free-electrons.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2015-09/txt/msg00033.txt.bz2 Thomas, > support only a smaller subset of the gcc/binutils/C library versions, > remove seldom used configuration options, etc. My main goal is use CT-NG to build an arm-none-eabi compiler. This is currently not full supported by CT-NG, at least with all the options the original build script is using. But I am very happy to have all the current options and selections which makes my life easier. A solution might be to enable some of the options only in experimental mode or to introduce a new mode, which allows only a few version combinations. If the new "Expert Mode" is selected, then you will get all the options to change the versions. > For example, Crosstool-NG > does not ensure that the proper cloog/mpc/gmp version is selected for a > given version of gcc At least for ClooG/isl I just implemented this. But you are right, who has the time to check all the possible combinations. > I think you might be confusing complexity with length. The current build > scripts may be long, but if it's just a list of: > > if [ "${CT_CC_CXA_ATEXIT}" = "y" ]; then > extra_config+=("--enable-__cxa_atexit") else > extra_config+=("--disable-__cxa_atexit") fi > > Then it is trivial to understand. If you replace that by something > "generic" that is shorter but in fact trickier to understand, there is no > real benefit. 100-gcc.sh uses "do_gcc_core_backend" for both the core and the final gcc, when building for bare-metal. I don't know why, but the do_gcc_core_backend function does not set the options for libssp and libquadmath and the handling of "CT_CC_GCC_USE_LTO" is different, too. So a generic "base class" for the gcc build might help to reduce such inconsistencies, because I guess this difference for both compilers is not intended. I guess it depends how Bryan wants to implement the generic script and how it can be tailored in the specific script. For example, I want to build newlib in two variants. This requires an additional build step "newlib-nano". However I will implement this, it is a complete copy of the newlib step with only 2..3 options changed/added. Having here a generic build script would reduce the work to implement this. > Now that you've moved to github for the code, maybe > https://travis-ci.org might help (at least for the non-randconfig cases)? Although this is intended for program regression tests, it can be used for CT-NG with this options (I guess): before_install: - sudo apt-get update -qq - sudo apt-get install -qq [packages list] -> used to install the packages required for CT-NG install: ./tests/config_cg_ng.sh -> will do bootstrap, configure --enable-local and make script: ./tests/run-tests.sh -> will execute CT-NG with the predefined configurations Note: a) ./tests is a new subdirectory for the travis-ci scripts. b) Someone needs to define predefined configs for the different variants to test and enter them into run-tests.sh Got this info about the configuration from here: http://docs.travis-ci.com/user/customizing-the-build/ BR Jasmin -- For unsubscribe information see http://sourceware.org/lists.html#faq