[cfe-dev] GCC compatibility layer going too far?

[Ludovic Courtès]

Hi,

Anton Korobeynikov <anton at korobeynikov.info> skribis:

> Hello
>
>> One of the reasons why the feature test passes is that
>> ‘clang -print-file-name=plugin’ returns GCC’s (!) header directory.
> What is "GCC's header directory"? Will you please provide an example?

$ clang --version
clang version 3.0 (tags/RELEASE_30/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix

$ ./result/bin/clang -print-file-name=plugin
/nix/store/k9lcfr49wdrad7j5p2pbiq2x0bmqd3pj-gcc-4.6.2/lib/gcc/x86_64-unknown-linux-gnu/4.6.2/plugin

$ gcc -print-file-name=plugin
/nix/store/32vc6sk2d4a3m88p821rxxwj83z7rf63-gcc-debug-4.6.2/lib/gcc/x86_64-unknown-linux-gnu/4.6.2/plugin

Thanks,
Ludo’.