Quoting Eric Anholt (2018-06-08 09:10:35)
> Dylan Baker writes:
>
> > [ Unknown signature status ]
> > Quoting Eric Anholt (2018-06-07 14:34:02)
> >> Dylan Baker writes:
> >>
> >> > The reason we restrict the use of ASM when cross compiling is that there
> >> > is a C based generator (mtypes)
Dylan Baker writes:
> [ Unknown signature status ]
> Quoting Eric Anholt (2018-06-07 14:34:02)
>> Dylan Baker writes:
>>
>> > The reason we restrict the use of ASM when cross compiling is that there
>> > is a C based generator (mtypes) that must be run as part of the build
>> > process, and it
Quoting Eric Anholt (2018-06-07 14:34:02)
> Dylan Baker writes:
>
> > The reason we restrict the use of ASM when cross compiling is that there
> > is a C based generator (mtypes) that must be run as part of the build
> > process, and it must be built for the host architecture. In the case of
> >
Dylan Baker writes:
> The reason we restrict the use of ASM when cross compiling is that there
> is a C based generator (mtypes) that must be run as part of the build
> process, and it must be built for the host architecture. In the case of
> an x86 host and an x86_64 build machine this is
On Thursday, 2018-06-07 09:19:29 -0700, Dylan Baker wrote:
> The reason we restrict the use of ASM when cross compiling is that there
> is a C based generator (mtypes) that must be run as part of the build
> process, and it must be built for the host architecture. In the case of
> an x86 host and
The reason we restrict the use of ASM when cross compiling is that there
is a C based generator (mtypes) that must be run as part of the build
process, and it must be built for the host architecture. In the case of
an x86 host and an x86_64 build machine this is possible as long as the
host and
