Now I know not to hit "enter" to go from one field to another. Maybe submitting the error report when the user hits "enter" should be disabled. I'm getting many error messages in stage1 of the bootstrap process of the form banach-8% grep 'invalid character' build.log | sort | uniq -c 1 ../../../gcc/fixinc/genfixes: invalid character 45 in exportstr for OBJS-onestep 1 ../../gcc/fixproto: invalid character 45 in exportstr for OBJS-onestep 1 ../../gcc/genmultilib: invalid character 45 in exportstr for OBJS-onestep 5 ../../gcc/mkconfig.sh: invalid character 45 in exportstr for OBJS-onestep 24 ../../gcc/move-if-change: invalid character 45 in exportstr for OBJS-onestep 1 ../../gcc/opts.sh: invalid character 45 in exportstr for OBJS-onestep 1 ../../gcc/scan-types.sh: invalid character 45 in exportstr for OBJS-onestep 2 ./fixinc.sh: invalid character 45 in exportstr for OBJS-onestep 1 /home/c/lucier/programs/gcc/gcc-3.4/gcc/fixinc/mkfixinc.sh: invalid character 45 in exportstr for OBJS-onestep 359 /local/bin/bash: invalid character 45 in exportstr for OBJS-onestep 1 mklibgcc: invalid character 45 in exportstr for OBJS-onestep I'm using this version of bash and gcc: banach-9% /local/bin/bash --version GNU bash, version 2.04.0(1)-release (sparc-sun-solaris2.8) Copyright 1999 Free Software Foundation, Inc. banach-10% gcc --version gcc (GCC) 3.3 Copyright (C) 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
char 45 is '-' so it looks like exportstr on solaris does not like '-' in the string.
I don't see them with ksh, which is the recommended shell to bootstrap the compiler with on Solaris. Could you try to bootstrap with it?
This is not a GCC bug but rather a bash bug, report it to them.