This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Why is building a cross compiler "out-of-the-box" always broken?


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]