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. This means that
> any compilation done with -mips32 will generate a warning during
> compilation. Unfortunately, this means that I have configure
I think you need to fix this problem rather than trying more and more
complicated workarounds. Essentially, the spec in OPTION_DEFAULT_SPECS
can't simply be "%{!msynci:%{!mno-synci:-m%(VALUE)}}" - it needs to be
something more complicated that avoids passing -msynci when it won't be
supported, or else it needs to pass an internal -msynci-if-supported
option which acts like -msynci except for not causing a warning.
--
Joseph S. Myers
jos...@codesourcery.com
