extending crosstool to allow simultaneous executions

[Dan Kegel]

Steven Scholz wrote:
>>   is it reasonable to extend crosstool slightly to allow simultaneous
>> invocations if you're using the same TARGET and TOOLCOMBO, but just
>> want to change something trivial -- say, some CONFIG flags?
>>
>>   as an example (and something i'm going to post on shortly), i might
>> want to start two simultaneous runs building a chain for SH3, but one
>> for big-endian and one for little-endian.  at the moment, i can't do
>> that since the script "all.sh" has, hardcoded, the lines:
>>
>>   TOOLCOMBO=$GCC_DIR-$GLIBC_DIR
>>   BUILD_DIR=`pwd`/build/$TARGET/$TOOLCOMBO

Yes, it's reasonable, but the way I'd suggest you do it is by
encoding the endian change in the TARGET name.  First, find out
if there is already a convention in the gcc sources:
   cd gcc-3.3.3/gcc
   grep sh3 config.gcc
This finds
         sh3e*) target_cpu_default="SELECT_SH3E" ;;
         sh3*)  target_cpu_default="SELECT_SH3" ;;
         sh3e[lb]e*) target_cpu_default="SELECT_SH3E" ;;
         sh3e[lb]*) target_cpu_default="SELECT_SH3" ;;
         sh3e*) target_cpu_default="SELECT_SH3E" ;;
         sh3*) target_cpu_default="SELECT_SH3" ;;
So you should try
   sh3eb-unknown-linux-gnu
   sh3el-unknown-linux-gnu
Alternate, the 2nd field in the target name is usually completely arbitrary,
so you could also try
   sh3-bigendian-linux-gnu
   sh3-littleendian-linux-gnu
or something similar.

> BTW I suggest
> 
>     TOOLCOMBO=$GCC_DIR-$GLIBC_DIR-$LINUX_DIR
> 
> since I use gcc-3.3.3-glibc-2.3.2-linux-2.6.8 _and_ 
> gcc-3.4.2-glibc-2.3.3-linux-2.4.27.

My impression was that you could use one toolchain for
any desired range of the linux kernel, so you can
have one toolchain for both 2.4 and 2.6.  Only reason
to have separate ones is a tiny savings in syscall interface
size.  I haven't heard of an example of really needing
separate ones (has anyone?).
- Dan

-- 
Trying to get a job as a c++ developer?  See http://kegel.com/academy/getting-hired.html

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com