From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7488 invoked by alias); 15 Jul 2012 17:30:19 -0000 Received: (qmail 7480 invoked by uid 22791); 15 Jul 2012 17:30:19 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,KHOP_THREADED,NML_ADSP_CUSTOM_MED,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from plane.gmane.org (HELO plane.gmane.org) (80.91.229.3) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 15 Jul 2012 17:30:06 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SqSdw-0001Fp-HV for crossgcc@sources.redhat.com; Sun, 15 Jul 2012 19:30:04 +0200 Received: from pool-71-182-229-106.pitbpa.fios.verizon.net ([71.182.229.106]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 15 Jul 2012 19:30:04 +0200 Received: from mrz.vtl by pool-71-182-229-106.pitbpa.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 15 Jul 2012 19:30:04 +0200 To: crossgcc@sources.redhat.com From: Maurizio Vitale Subject: Re: GCC support libraries and sysroot Date: Mon, 16 Jul 2012 08:03:00 -0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) 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-07/txt/msg00044.txt.bz2 Michael Hope linaro.org> writes: > > 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. > I'm exploring similar sysroot setups (but in my case I want the sysroot to work for both gcc and clang). Other than size, what would go wrong with having all sysroots including the GCC's support libraries and whatever additional library the specific sysroot introduces? Obviously it would require redistribution of all sysroot tarfiles whenever the compiler toolchain changes, but other than that and size, I don't see problems. I've just started with this setup, so I might be missing the obvious. Maurizio -- For unsubscribe information see http://sourceware.org/lists.html#faq