Re: PR4186: cross-compilation, $ARCH

["Frank Ch. Eigler" <fche at redhat dot com>]

Hi -

On Tue, Aug 25, 2009 at 10:13:15AM -0500, David Smith wrote:
> [...]
> > I don't know.  We'd have to handle things like
> >   %( arch == "i686" %? /*A*/ %: /*B*/ %) 
> > and also
> >   %( arch == "i686" %? /*A*/ %: %( arch == "i386" %? /*B*/ %: /*C*/ %) %)
> > 
> > - FChE
> 
> I'm not sure I explained myself well about the aliases (or I didn't read
> your response correctly).  What I'm suggesting is that the following
> *both* match:
> 
> %(arch == "i686" %? /*A*/ %)
> 
> %(arch == "i386" %? /*A*/ %)
>
> i.e., in the translator, let arch matching be done with a wildcard.  In
> the case of x86, it would be like checking the user's string against the
> regular expression 'i[3-6]86'.

Right, the problem occurs in the "else" case, where some hypothetical
script tested vs. i686 as distinct from i386.

> I just poked through the tapsets, and it seems that when i386/i686
> are looked at, both cases appear to be handled the same anyway, so
> it wouldn't really matter if both matched.

Sure, we can adjust all our script code for consistency.  That leaves
only existing third-party scripts as a possible rationale for backward
compatibility hacks.

- FChE