From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9779 invoked by alias); 6 May 2012 16:37:07 -0000 Received: (qmail 9569 invoked by uid 22791); 6 May 2012 16:37:05 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.free-electrons.com (HELO mail.free-electrons.com) (88.190.12.23) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 06 May 2012 16:36:52 +0000 Received: by mail.free-electrons.com (Postfix, from userid 106) id 768E4192; Sun, 6 May 2012 18:36:51 +0200 (CEST) Received: from skate (humanoidz.org [82.247.183.72]) by mail.free-electrons.com (Postfix) with ESMTPSA id 3F8D712A; Sun, 6 May 2012 18:36:44 +0200 (CEST) Date: Sun, 06 May 2012 16:37:00 -0000 From: Thomas Petazzoni To: Michael Hope Cc: crossgcc@sourceware.org Subject: Re: GCC support libraries and sysroot Message-ID: <20120506183641.5d26bcb4@skate> In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes 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 X-SW-Source: 2012-05/txt/msg00006.txt.bz2 Hello Michael, Le Fri, 23 Mar 2012 14:22:55 +1300, Michael Hope a =C3=A9crit : > Hi there. Why does crosstool-NG create a symlink from > $tuple/$sysroot/lib to $tuple/lib? It causes GCC to install support > libraries like libgcc_s.so into the sysroot instead of the default > location which makes it tricky to replace the sysroot later. On the other hand, this was making things simple and easy for tools like Buildroot to leverage the pre-built Linaro toolchains. The Linaro, Sourcery CodeBench, Crosstool-NG and Buildroot toolchains all behaved the same by installing all the libraries into the sysroot, so it was easy to support all of them: we just copy the complete sysroot into a "staging" directory, into which we add more libraries/headers as we build stuff for the target. Since Linaro 2012.03 (and therefore 2012.04), this simple idea doesn't work anymore as Linaro toolchains have important stuff installed outside of the sysroot, which makes it a lot more complicated for Buildroot to handle (and I guess possibly other similar tools). Best regards, Thomas --=20 Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com -- For unsubscribe information see http://sourceware.org/lists.html#faq