RE: architecture issues

[Sebastian Reitenbach]

nicola.pero@meta-innovation.com wrote: 
> 
> > Nevertheless, I more or less dropped the usage of the config.guess at 
all, 
> > and just set 
> >  host_alias=`gnustep-config --variable=GNUSTEP_HOST`
> > in the NONE clause of the case statement, and it worked well.
> >
> > Could that be considered a safe method everywhere?
> 
> Yes :-)
> 
> You should be able to manage to get the same results using config.guess 
> if you use apply the clean_cpu.sh, clean_os.sh etc. scripts to the 
> results - the same that gnustep-make is using.
> 
> But the simplest approach is just to rely on the same variables that 
gnustep-make
> uses, so you should never have a problem - even if gnustep-make changes in 
some
> way the host values in the future.  And gnustep-config is the "official" 
way 
> of getting these variables in gnustep-make v2. :-)

ok, that sounds "save" enough ;)
then I'm taking this route.

thanks a lot
Sebastian