From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7348 invoked by alias); 23 Mar 2012 01:23:30 -0000 Received: (qmail 7340 invoked by uid 22791); 23 Mar 2012 01:23:29 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-wg0-f41.google.com (HELO mail-wg0-f41.google.com) (74.125.82.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 23 Mar 2012 01:23:16 +0000 Received: by wgbds1 with SMTP id ds1so727876wgb.0 for ; Thu, 22 Mar 2012 18:23:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type :x-gm-message-state; bh=EhFQUcQ3S5ugwArc1QFuYcx+4PtLzpf+5lZK1ZetDYM=; b=OFbEc3R80nQ/4ThrMvY6n0IfQjm7UVm4Fs8KaRYoFiTaRIyeK/LzJbskPvP4gQxdNt JVnW7oPSFtSAfHRN6M2VM6wH1SiHmv4n4NpY6h+lLTFxzehLzngCiN7RM3yVFm659XjS I4KdjXszg5FedhU5fpvYnnl/w6xdtI0Lf1nK8kDHjQhtLPO0jsV/nPW2K+9sWnd2FVdy 4vwoJn26CsepBPkiSsFL3BuK77ZDDq1ns/1Q41c77ahFZtsYU+wYxgqdsWhfHXg0usw8 UWzmC6UQohKl1PwstIxi6Vpka1QuslGlRhBgyBA0MkIP/8E7kM5I/b9SG5qRp9jRvrvG 55Ng== Received: by 10.216.139.29 with SMTP id b29mr5957176wej.55.1332465795171; Thu, 22 Mar 2012 18:23:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.170.81 with HTTP; Thu, 22 Mar 2012 18:22:55 -0700 (PDT) From: Michael Hope Date: Fri, 23 Mar 2012 01:23:00 -0000 Message-ID: Subject: GCC support libraries and sysroot To: crossgcc@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkZoBlN2ool3IpJ0QnMETwrM7/DDVwCvsROxkxO9Svx3L+BBOBmp0jjyNanqgXZ7BQ34CLB 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-03/txt/msg00046.txt.bz2 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. For our binary builds we plan to supply a few different sysroots including a minimal libc, developer image with GTK and X, and a desktop image with a wide range of packages. They'll come as tarballs and the intent is for people to delete the old $tuple/$sysroot and extract the new one in its place. Currently this means that the support libraries will also get deleted. The target comes with these libraries preinstalled. -- Michael -- For unsubscribe information see http://sourceware.org/lists.html#faq