From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 63886 invoked by alias); 21 Mar 2017 17:30:35 -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 63863 invoked by uid 89); 21 Mar 2017 17:30:34 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=H*r:sk:crossgc X-HELO: mail-vk0-f41.google.com Received: from mail-vk0-f41.google.com (HELO mail-vk0-f41.google.com) (209.85.213.41) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 21 Mar 2017 17:30:25 +0000 Received: by mail-vk0-f41.google.com with SMTP id x75so101835011vke.2 for ; Tue, 21 Mar 2017 10:30:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yohpIQIMcMIL/5Wbn2n+MfyPd5JoPxscY44lJ5wKt2E=; b=Z/xBgiuKEEBl1LHXhflP4lhZ1j2a3N3kujp2pSCfQbmIZLp/2F9uF6sAOCwt2L0nV9 iqCW3ozi6zyn5gH/UVuQybTkXedo4r31ebwcpFpzvIX62pIqf35/G5I9cSXhT+haEEL9 Vusopu1Mb19DkX2j7nxPhoOrHb8FykBDNV3+/r0MH1iuGwA03RH7oYIHvLC1VEOUeGgD jg9Z0Sc3L+P31AbbY/UzpFECg3XiSqJneDBw9qPM+ncwnxmd3/tQFcun3HpoJGY8jf41 983JhAwntS3Fm6TnNV4Gq9KGgMH4c9kPxoSWzNY0SmkZq+Gxn7NgL5NnO4ewoLQAVZ4T ldDg== X-Gm-Message-State: AFeK/H0qHADUIXPUKfhpzU/b/f27znPKWx0lHxgEaNiTygeRy7oAzkfh2v0RZBoYyGs1AiI3ypouEzlyMt/2dA== X-Received: by 10.176.24.161 with SMTP id t33mr12862154uag.37.1490117424418; Tue, 21 Mar 2017 10:30:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.20.2 with HTTP; Tue, 21 Mar 2017 10:30:24 -0700 (PDT) In-Reply-To: <3c543531-7142-87bb-47b7-9f6b8e669526@att.net> References: <3c543531-7142-87bb-47b7-9f6b8e669526@att.net> From: Justin Chen Date: Tue, 21 Mar 2017 17:30:00 -0000 Message-ID: Subject: Re: Some Questions To: Alexey Neyman Cc: crossgcc@sourceware.org Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2017-03/txt/msg00032.txt.bz2 On Mon, Mar 20, 2017 at 10:37 PM, Alexey Neyman wrote: > On 03/20/2017 03:02 PM, Justin Chen wrote: >> >> Hello all, >> >> I have two questions, some input would be awesome. :) >> >> 1. Are there any plans to support LSB based builds? > > I am not sure what you want from crosstool-NG in this respect. If you are > talking about the layout of the resulting filesystem, crosstool-NG is but a > little piece - the construction of the filesystem is typically handled by > other tools such as buildroot. Perhaps, you need to explain this a bit more. Ah sorry! I can explain more. I was wondering if there were plans to support building toolchains with the LSB-sdk. http://linuxtesting.org/lsb_sdk Basically, the sdk will help compile the toolchain to follow the LSB standard. This means the resulting toolchain will be more portable between different linux systems. https://wiki.linuxfoundation.org/lsb/start We will need to download the sdk, setup the environment, then change a few configure options here and there. >> >> 2. I am building multiple cross-compilers and throwing them into the >> same toolchain. I am doing this by running separate builds into the >> same out dir. This works nicely, however, host components need to be >> rebuilt for each configuration(which waste some time). Would you guys >> be interested in a feature where you can pass multiple config files >> and have crosstools-ng build all of them in one go? (I can put a patch >> together, if you guys would be willing to accept such a feature) > > It would be interesting but I am not sure how much we can safely share. Some > host components are still configured for a particular target. > Others may be shared, but this would place certain requirements on the > host/build configuration parts (which obviously must be the same for all of > them). > BTW, by "out dir" do you mean the build directory or the installation > directory? The installation directory. > > I am not totally opposed to this, but before you start hacking around, I'd > suggest you make a small write-up on *what* you intend to share and *how* > you are going to check that it is actually shareable (e.g., fail? create a > separate build directory for each different config? anything else?) Sounds good to me. I still need to work out the details myself, but if it sounds reasonable... Sure! I can do a small write-up first. Thanks, Justin > > Regards, > Alexey.