From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2522 invoked by alias); 30 Nov 2006 01:25:51 -0000 Received: (qmail 2500 invoked by uid 22791); 30 Nov 2006 01:25:49 -0000 X-Spam-Check-By: sourceware.org Received: from dessent.net (HELO dessent.net) (69.60.119.225) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 30 Nov 2006 01:25:41 +0000 Received: from localhost ([127.0.0.1] helo=dessent.net) by dessent.net with esmtp (Exim 4.61) (envelope-from ) id 1GpagE-0002Oe-DT; Thu, 30 Nov 2006 01:25:38 +0000 Message-ID: <456E3312.7BE37777@dessent.net> Date: Thu, 30 Nov 2006 01:25:00 -0000 From: Brian Dessent Reply-To: gcc-help@gcc.gnu.org X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: Ulf Magnusson CC: gcc-help@gcc.gnu.org Subject: Re: Unclear documentation on building GCC together with binutils References: <456D45FB.DF049260@dessent.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2006-11/txt/msg00372.txt.bz2 Ulf Magnusson wrote: > Just to check that I have understood the procedure and read the > symlink-tree script properly, would the following be the right way to > combine gcc and binutils using the symlink-tree script? > > tar -xvjf gcc-recent.release.tar.bz2 > tar -xvjf binutils-not.so.recent.release.tar.bz2 > cd binutils-not.so.recent.release > ./symlink-tree ../gcc-recent.release > configure ... > make ... I guess that would work, but you might want to try a build to verify. I have not personally used symlink-tree. I think a more common approach that you'll find in tutorials is to create a new dir, that consists of entirely links: tar jxf gcc-?.?.?.tar.bz2 tar jxf binutils-?.?.?.tar.bz2 mkdir combined && cd combined ../gcc/symlink-tree ../binutils-?.?.? ../gcc/symlink-tree ../gcc-?.?.? You could also do this with "cp -puR" or tar to merge the trees (if you don't care about disk space) or with "cpio -l" and hard links, as suggested in . > Oh, and shouldn't srcdir be quoted when it's assigned and used in the > script, to correctly handle paths with whitespace in them? Probably. Although having pathnames with spaces in them will probably throw a wrench into the build in other places as well so I'd suggest avoiding it if at all possible. I would say file a bug report for any place where an unquoted argument causes a failure due to spaces in filenames, but I don't know if the official stance is "that isn't supported" or not. Brian