bug#342: Lnx-bbc-devel] Re: bug#342: we need to make glibc's autoconf believe that it should cross-compile

begin  The ASCII Floating Head of Seth David Schoen  quotation:
> If we do this, is there any problem in using (a) our gcc, (b) our
> binutils, or (c) our glibc to build things (1) in our gar tree to
> run on the BBC, (2) on the BBC to run on the BBC, (3) on the BBC to
> run on another host system?
> 
> I would not be offended if the answer to some of those were "mu".

	The answer is no for all of the lettered questions.  Possibly
"mu" for all of the numbered.  The arch string only affects the arch
string reported by glibc etc on the running system.  There are also
precious few packages where we specify --build and --host, glibc being
the only big one I can think of (aside from nate's recent ccache
checkin).

	1 and 2 are no, to my estimation.  The whole purpose of these
flags is precisely what we attempt to do.  3 seems irrelevant to me.
If you want a program for your other system, compile it.  We're
internally consistent, and that's all that matters to me.  It's likely
that our binaries would run on other systems, but I really don't care.

> I'm assuming that this arch string does not affect the actual binary
> format of anything, but I wonder if it can confuse configure scripts
> or tools run from configure scripts.  If only I were able to take
> Nick's tutorial, I'm sure my confusion about these effects would be
> cleared up quickly.

	I'm delivering it this monday at 1pm, if you have a few
thousand dollars to cough up.  Also, a lot of these proposed changes
are the result of Daniel Jacobowitz schooling me with the rather more
advanced autoconf-fu.

-- 

end
 
 Support your droogs!