fontconfig: Force use of c++ linker

fontconfig: Force use of c++ linker

This is really silly, but gyp doesn't seem to track if a static_library
contains C++ code and needs a C++ link step. So our copy of libxml
breaks us by containing a little bit of (chromium-added) C++ code. This
is really a correctness issue in the build system.

BUG=445627
TEST=linux_ecs_ozone tryjob

Committed: https://crrev.com/0540e174312591a9f9b71e557810869eacd66929
Cr-Commit-Position: refs/heads/master@{#315138}

[spang, 2015-02-06 22:12:14]

spang@chromium.org changed reviewers:
+ dnicoara@chromium.org

[spang, 2015-02-06 22:13:30]

On 2015/02/06 22:12:14, spang wrote:

see also 

http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_ecs_ozone...

(failed tryjob for https://codereview.chromium.org/900343002/)

[dnicoara, 2015-02-06 22:37:42]

lgtm

[spang, 2015-02-06 23:27:52]

The CQ bit was checked by spang@chromium.org

[commit-bot: I haz the power, 2015-02-06 23:28:37]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/872493004/1

[commit-bot: I haz the power, 2015-02-06 23:52:28]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-02-06 23:53:00]

Patchset 1 (id:??) landed as
https://crrev.com/0540e174312591a9f9b71e557810869eacd66929
Cr-Commit-Position: refs/heads/master@{#315138}

[Nico, 2015-02-07 00:21:15]

thakis@chromium.org changed reviewers:
+ thakis@chromium.org

[Nico, 2015-02-07 00:21:15]

(fyi: Another option is to add -lstdc++:
https://codereview.chromium.org/854753002/diff/100001/third_party/mesa/mesa.g...)

[spang, 2015-02-09 19:00:52]

On 2015/02/07 00:21:15, Nico wrote:
> (fyi: Another option is to add -lstdc++:
>
https://codereview.chromium.org/854753002/diff/100001/third_party/mesa/mesa.g...)

I thought about that but I feel we should use the right frontend altogether (g++
or clang++). That way there's no need to make any assumptions about toolchain
internals.