On Thursday 18 July 2013 16:59:52 Matt Turner wrote:
On Mon, Feb 4, 2013 at 6:27 PM, Mike Frysinger vap...@gentoo.org wrote:
The current gen_matypes logic assumes that the host compiler will produce
information that is useful for the target compiler. Unfortunately, this
is not the case
On Mon, Feb 4, 2013 at 6:27 PM, Mike Frysinger vap...@gentoo.org wrote:
The current gen_matypes logic assumes that the host compiler will produce
information that is useful for the target compiler. Unfortunately, this
is not the case whenever cross-compiling.
When we detect that we're
Mike Frysinger vap...@gentoo.org writes:
The current gen_matypes logic assumes that the host compiler will produce
information that is useful for the target compiler. Unfortunately, this
is not the case whenever cross-compiling.
When we detect that we're cross-compiling and using GCC, use
The current gen_matypes logic assumes that the host compiler will produce
information that is useful for the target compiler. Unfortunately, this
is not the case whenever cross-compiling.
When we detect that we're cross-compiling and using GCC, use the target
compiler to produce assembly from
I'm not familiar with with autotools to comment on those bits, but I think this
is a pretty neat idea.
This could be also when when cross compiling for windows w/ mingw.
Jose
- Original Message -
The current gen_matypes logic assumes that the host compiler will
produce
information
On Tue, Jan 31, 2012 at 6:07 PM, Mike Frysinger vap...@gentoo.org wrote:
The current gen_matypes logic assumes that the host compiler will produce
information that is useful for the target compiler. Unfortunately, this
is not the case whenever cross-compiling.
When we detect that we're
The current gen_matypes logic assumes that the host compiler will produce
information that is useful for the target compiler. Unfortunately, this
is not the case whenever cross-compiling.
When we detect that we're cross-compiling and using GCC, use the target
compiler to produce assembly from
