From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4788 invoked by alias); 26 Jan 2014 03:23: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 4777 invoked by uid 89); 26 Jan 2014 03:23:38 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-vc0-f194.google.com Received: from mail-vc0-f194.google.com (HELO mail-vc0-f194.google.com) (209.85.220.194) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Sun, 26 Jan 2014 03:23:37 +0000 Received: by mail-vc0-f194.google.com with SMTP id hu8so797000vcb.9 for ; Sat, 25 Jan 2014 19:23:34 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.59.8.100 with SMTP id dj4mr2165ved.55.1390706614744; Sat, 25 Jan 2014 19:23:34 -0800 (PST) Received: by 10.58.108.200 with HTTP; Sat, 25 Jan 2014 19:23:34 -0800 (PST) Date: Sun, 26 Jan 2014 03:23:00 -0000 Message-ID: Subject: Toolchain Usage From: Me Me To: crossgcc@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-SW-Source: 2014-01/txt/msg00059.txt.bz2 I'm looking into using crosstool-ng as backend for generating my toolchains. I love the software and it is incredibly slick. Right now, my current toolchain includes an extra 20 or so packages in it, so after entering into a chroot, each package would have everything it needed to build and install. But from what I have read, this seems to go against the spirit of the toolchain being as minimal as possible to only generate code for the target architecture. I have seen many implementations which do not use chroot at all and just override a slew of environment variables to build the final system (PATH, CFLAGS, LDFLAGS, etc). Chrooting seems much safer from the host polluting the target system (especially if the packages that get built don't use some type of autotools or respect environment variables). On the other hand, I would rather prefer the simplicity of not cramming extra packages into the toolchain unnecessarily. In the future, I hope to be able to utilize crosstool-ng to generate my toolchains for building each of the packages in the final system; all without chrooting. My current process: 1) Use host system to generate/run toolchain for the target architecture. 2) Use toolchain/chroot to generate final system. Remove toolchain when finished. 3) Use final system/chroot to generate rest of the packages. Ideal process: 1) Use host system to generate/run toolchain for the target architecture. 2) Use toolchain to generate packages in the final system. So, 1) Is chrooting a valid/preferred way to utilize the toolchain to build the final system? 2) If not, how can I be sure that I don't pollute the final system with includes/linking from the host system? 3) What are the pros/cons of both methods? Thanks, Jer -- For unsubscribe information see http://sourceware.org/lists.html#faq