On Tue, 2012-06-19 at 20:59 +, Joseph S. Myers wrote:
> On Tue, 19 Jun 2012, Steve Ellcey wrote:
>
> > I am building a multilib mips compiler using '--with-synci' on the
> > configure line. This means that gcc will pass the '-msynci' option
> > to cc1 by default. The problem occurs when on
On Tue, 19 Jun 2012, Steve Ellcey wrote:
> I am building a multilib mips compiler using '--with-synci' on the
> configure line. This means that gcc will pass the '-msynci' option
> to cc1 by default. The problem occurs when one of my multilib
> targets (like -mips32) does not support synci. T
"Steve Ellcey " writes:
> I am building a multilib mips compiler using '--with-synci' on the
> configure line. This means that gcc will pass the '-msynci' option
> to cc1 by default. The problem occurs when one of my multilib
> targets (like -mips32) does not support synci. This means that
>
I am trying to fix a multilib build problem and am hoping a build expert
can help me figure out a fix/workaround to my problem.
I am building a multilib mips compiler using '--with-synci' on the
configure line. This means that gcc will pass the '-msynci' option
to cc1 by default. The problem o
