[cfe-commits] Ping^2: Fix for bug 11060: configure --target does not work

Sebastian Pop spop at codeaurora.org
Fri Oct 21 14:10:28 PDT 2011

On Fri, Oct 21, 2011 at 3:43 PM, Eric Christopher <echristo at apple.com> wrote:
> I'm not quite convinced we want to do this at the moment. I understand the
> desire to attempt to make clang feel like gcc for cross compilation, but
> given that clang can compile to multiple targets simultaneously I don't
> think that this is the correct path to take.

I understand that clang is more flexible than gcc as it can target any
of the backends that are built.  My patches do not change that.
The patches only change the value of the default target when no
other flags are used to specify a target.

> Can you give a rationale for wanting this change?

First, my patches conserve the semantics of configure if you do not
explicitly set the --target flag.  If you want the current behavior, then
you can omit --target and the configure script will infer the value of
target from the host.

My patches make --target useful, as the current semantics of --target
is that of nop.  The target backed should default to the one specified
by the user at configure time.

Also, without my patches I do not see how clang configured with
../configure --enable-targets=arm --target=arm
would work on an x86 host machine if you explicitly disable the x86

Qualcomm Innovation Center, Inc is a member of Code Aurora Forum

More information about the cfe-commits mailing list