From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11564 invoked by alias); 16 Nov 2014 18:09:44 -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 11546 invoked by uid 89); 16 Nov 2014 18:09:42 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 X-HELO: BLU004-OMC3S12.hotmail.com Received: from blu004-omc3s12.hotmail.com (HELO BLU004-OMC3S12.hotmail.com) (65.55.116.87) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA256 encrypted) ESMTPS; Sun, 16 Nov 2014 18:09:40 +0000 Received: from BLU437-SMTP92 ([65.55.116.73]) by BLU004-OMC3S12.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Sun, 16 Nov 2014 10:09:38 -0800 X-TMN: [vuPBzxuSi1r0vbuY2z8QAd6iVzz/6s0N] Message-ID: From: Bill Pringlemeir To: Mauro Condarelli CC: crossgcc@sourceware.org Subject: Re: building a cross-native for arm References: <543A6165.2060400@mailgate> <543AE181.8050500@mailgate> Date: Sun, 16 Nov 2014 18:09:00 -0000 In-Reply-To: <543AE181.8050500@mailgate> (Mauro Condarelli's message of "Sun, 12 Oct 2014 22:16:01 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-IsSubscribed: yes X-SW-Source: 2014-11/txt/msg00006.txt.bz2 On 12 Oct 2014, mauro@mailgate.soft-in.com wrote: > I'm answering to myself to add a few comments. > 0) cross-compiler seems to work ok (arm-mcon-linux-gnueabi) I am > "deploying" it merely doing a: > ( cd /usr/local/bin ; ln -s >> HOME/x-tools/arm-mcon-linux-gnueabi/bin/* . ) > on my build machine. > 1) I got to the end of cross-native toolchain compilation (disabling > GDB), but I'm unable to make it run on target board because of many > missing libs. > 2) I tried using the "staging", but that doesn't fit well (IF I used > it correctly!) because many libs are pushed in the standard /lib & > /usr/lib, while I would like to have some sort of self-contained > package (probably to deploy it in > /usr/local/arm-mcon-linux-gnueabi/... or something similar). Investigate the populate scripts. It should be names something like 'arm-mcon-linux-gnueabi-populate'. See: http://crosstool-ng.org/git/crosstool-ng/tree/scripts/populate.in http://crosstool-ng.org/git/crosstool-ng/tree/docs/5%20-%20Using%20the%20toolchain.txt#137 You can use 'chroot' to test the compiler on the target. Ie, make a complete parallel directory structure and use it to test a shell. You can also change your mount options and linux 'root=' to point to alternate mount points. This is a fairly difficult topic that is really outside of ct-ng. You should research 'linux+root filesystem'. It may also be possible to have two sets of 'libc' existing at the same time. However, this is not very efficient and you would want to eliminate this eventually. It seems to make most sense to start with either a completely different 'mount point' or directory and use 'chroot' to test it out. Fwiw, Bill Pringlemeir. -- For unsubscribe information see http://sourceware.org/lists.html#faq