From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-140074-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 32429 invoked by alias); 22 Aug 2007 21:23:45 -0000
Received: (qmail 32325 invoked by uid 22791); 22 Aug 2007 21:23:45 -0000
X-Spam-Check-By: sourceware.org
Received: from pfepb.post.tele.dk (HELO pfepb.post.tele.dk) (195.41.46.236)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 22 Aug 2007 21:23:42 +0000
Received: from x1-6-00-0f-9f-c6-3e-90 (x1-6-00-0f-9f-c6-3e-90.k75.webspeed.dk [80.197.1.215]) 	by pfepb.post.tele.dk (Postfix) with ESMTP id 79903A5003C; 	Wed, 22 Aug 2007 23:23:38 +0200 (CEST)
Received: from x1-6-00-0f-9f-c6-3e-90 (localhost.localdomain [127.0.0.1]) 	by x1-6-00-0f-9f-c6-3e-90 (8.14.0/8.14.0) with ESMTP id l7MLNdDl020634; 	Wed, 22 Aug 2007 23:23:39 +0200
Received: (from rask@localhost) 	by x1-6-00-0f-9f-c6-3e-90 (8.14.0/8.14.0/Submit) id l7MLNclp020633; 	Wed, 22 Aug 2007 23:23:38 +0200
Date: Wed, 22 Aug 2007 21:47:00 -0000
From: Rask Ingemann Lambertsen <rask@sygehus.dk>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: gcc@gcc.gnu.org
Subject: Re: Why is building a cross compiler "out-of-the-box" always 	broken?
Message-ID: <20070822212338.GY25795@sygehus.dk>
References: <46C603EC.4070004@ou.edu> <1d2196e08f6a3da5183e4aa9d9fa06bd@kernel.crashing.org> <20070818201155.GZ25795@sygehus.dk> <46C7FAB5.8000702@gnu.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46C7FAB5.8000702@gnu.org>
User-Agent: Mutt/1.5.14 (2007-02-12)
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
X-SW-Source: 2007-08/txt/msg00380.txt.bz2

On Sun, Aug 19, 2007 at 10:09:25AM +0200, Paolo Bonzini wrote:
> 
> >   Thanks for reminding me to ping that patch.
> 
> Could you try moving this case statement
> 
> +	case "$target" in
> +	  i[[3456]]86-*-elf* | i[[3456]]86-*-coff*)
> +	    libgloss_dir=i386
> +	    ;;
> +	  m68hc11-*-* | m6811-*-* | m68hc12-*-* | m6812-*-*)
> +	    libgloss_dir=m68hc11
> +	    ;;
> 
> above in another "case $target in" statement?

   I don't understand what you want it to look like. Your explanation sounds
to me like

	case "$target" in
	  i[[3456]]86-*-elf* | i[[3456]]86-*-coff*)
	    libgloss_dir=i386
	    ;;
	  m68hc11-*-* | m6811-*-* | m68hc12-*-* | m6812-*-*)
	    libgloss_dir=m68hc11
	    ;;
	esac

	case "$target" in
	... rest of cases go here ...

	  *)
	    libgloss_dir=${cpu}
	    ;;
	esac

but then the default of the second case construct will override libgloss_dir
from the first one, if I'm not missing something here.

-- 
Rask Ingemann Lambertsen