From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3725 invoked by alias); 12 Oct 2014 20:16:29 -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 3716 invoked by uid 89); 12 Oct 2014 20:16:28 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.6 required=5.0 tests=AWL,BAYES_50,NO_DNS_FOR_FROM,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 X-HELO: ambassador.soft-in.com Received: from mail.soft-in.com (HELO ambassador.soft-in.com) (178.255.189.211) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 12 Oct 2014 20:16:26 +0000 Received: from localhost (localhost [127.0.0.1]) by ambassador.soft-in.com (Postfix) with ESMTP id F0E4B1041141 for ; Sun, 12 Oct 2014 22:16:23 +0200 (CEST) Received: from ambassador.soft-in.com ([127.0.0.1]) by localhost (ambassador.soft-in.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id E5qZiPaereru for ; Sun, 12 Oct 2014 22:16:12 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by ambassador.soft-in.com (Postfix) with ESMTP id B4CD01041140 for ; Sun, 12 Oct 2014 22:16:12 +0200 (CEST) Received: from ambassador.soft-in.com ([127.0.0.1]) by localhost (ambassador.soft-in.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id IkP6Vo5cSRw2 for ; Sun, 12 Oct 2014 22:16:12 +0200 (CEST) Received: from [192.168.7.114] (host180-252-static.254-95-b.business.telecomitalia.it [95.254.252.180]) by ambassador.soft-in.com (Postfix) with ESMTPSA id 3BD37104113E for ; Sun, 12 Oct 2014 22:16:12 +0200 (CEST) Message-ID: <543AE181.8050500@mailgate> Date: Sun, 12 Oct 2014 20:16:00 -0000 From: Mauro Condarelli User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: crossgcc@sourceware.org Subject: Re: building a cross-native for arm References: <543A6165.2060400@mailgate> In-Reply-To: <543A6165.2060400@mailgate> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2014-10/txt/msg00010.txt.bz2 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). What am I doing wrong? TiA Mauro On 10/12/2014 01:09 PM, Mauro Condarelli wrote: > Hi, > first of all many thanks for the effort and time spent on crossgcc-NG. > This is my first attempt at using it, so I might be very mistaken > everywhere. > > I need a native compiler (and related stuff, including make and other > installation tools) running on a small ARM board (I wouldn't want to > cross-compile for it). > > I built the cross compiler (arm-mconc-linux-gnueabi) with almost no > problem, in spite of the very terse documentation I found. > Only stumbling was because I didn't have libncurses-dev installed on > my build system. > Now I have a nice $HOME/x-tools/arm-mconc-linux-gnueabi subdir. > > If I understand it correctly I now need to use this cross-gcc to build > the native. > I changed Tuple's vendor string to "mconn". > I activated the "canadian" type and selected "arm-conc-linux-gnueabi" > as Host system Tuple. > > First problem was ct-ng wouldn't find the cross-toolchain, so I > resorted to: > $ PATH=$HOME/x-tools/arm-mconc-linux-gnueabi/bin:$PATH ct-ng build > > This seems to work, but, building gdb, I get again the error about > "missing termcap library". > I presently disabled GDB to finish the build and test results, but > that's not a real solution, obviously. > > Is there some "tutorial" documentation available somewhere? I didn't > find any and, as said docs coming with crossgcc-NG seem a bit too terse. > > Other question: it seems the option about "Companion tools" seems to > apply to upgrade old tools running on build machine; is there a way to > build the same tools for the host (==target, in my case)? That would > be very useful. > > Last, but not least, I am a bit confused about what, exactly, I should > copy on the target machine and where, to use the generated native > toolchain. > Now cross-compilation of native has finished without errors and I have > a confusing PATH=$HOME/x-tools/arm-mconn-linux-gnueabi directory > ("..." stand for this directory): > 1) executable are in .../bin > 2) but .../include is empty and .../lib contains only the > gcc-specific stuff > 3) .../arm-mconn-linux-gnueabi/bin contains only binutils > (without prefix) > 4) .../arm-mconn-linux-gnueabi/include contains only "c++" subdir > 5) .../arm-mconn-linux-gnueabi/sysroot seems to have correct libs > and include, but has neither compiler nor binutils > What is the "approved" way to deploy all this stuff to target? > Sorry if these are very naive questions, I searched, but I couldn't > find an answer to them (shame on me). > > Thanks again and Regards > Mauro Condarelli > > -- > For unsubscribe information see http://sourceware.org/lists.html#faq > -- For unsubscribe information see http://sourceware.org/lists.html#faq