Received: by 10.100.243.21 with SMTP id q21mr10162682anh.5.1337685673154;
        Tue, 22 May 2012 04:21:13 -0700 (PDT)
X-BeenThere: chromium-...@chromium.org
Received: by 10.101.157.15 with SMTP id j15ls1195518ano.6.gmail; Tue, 22 May
 2012 04:21:04 -0700 (PDT)
Received: by 10.100.86.1 with SMTP id j1mr7993465anb.50.1337685664459;
        Tue, 22 May 2012 04:21:04 -0700 (PDT)
Received: by 10.100.86.1 with SMTP id j1mr7993464anb.50.1337685664441;
        Tue, 22 May 2012 04:21:04 -0700 (PDT)
Return-Path: <phajdan...@gmail.com>
Received: from mail-yx0-f169.google.com (mail-yx0-f169.google.com [209.85.213.169])
        by mx.google.com with ESMTPS id j6si8443893ani.81.2012.05.22.04.21.04
        (version=TLSv1/SSLv3 cipher=OTHER);
        Tue, 22 May 2012 04:21:04 -0700 (PDT)
Received-SPF: pass (google.com: domain of phajdan...@gmail.com designates 209.85.213.169 as permitted sender) client-ip=209.85.213.169;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of phajdan...@gmail.com designates 209.85.213.169 as permitted sender) smtp.mail=phajdan...@gmail.com; dkim=pass header...@gmail.com
Received: by yenm7 with SMTP id m7so6362254yen.0
        for <chromium-...@chromium.org>; Tue, 22 May 2012 04:21:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:from:date:x-google-sender-auth:message-id
         :subject:to:content-type;
        bh=Ncx8/POf2bXRFJUHdxEfWIx9Fyj2L3TK6ioXpvma6dk=;
        b=MPdWtVk4jx463VoTpVZa4H/dhXNFDeQRdQYKUa+kv/rMH165uI14YXddMjWZ7KEMFg
         qAuH7GvADmSVmIWO3Dl+WIQorSorXA62hCHTJQOPSHPdSngMQYXUhoO2b7FCwN0L/mXt
         ATyU33c+6ZCIxb1GoPW6g4m9ZRxjTMSrxJCDEBxB4XVEEc6iEpwgwZD2h4RuMJihGl+q
         mGYYubyfLvnIwzfx2/ayXmXCyJBH2EjUvFkqe3xcdCN2x07VPscj76sn6P2WwDXqnjSj
         YITOJnPXhCxC73QnuterS33C8Ru1mlJ0hjgF3LiutLtL6/V5GMh9v2/ETkSczKD9gGC3
         F/0A==
Received: by 10.236.179.106 with SMTP id g70mr11937518yhm.53.1337685664056;
 Tue, 22 May 2012 04:21:04 -0700 (PDT)
MIME-Version: 1.0
Sender: phajdan...@gmail.com
Received: by 10.146.150.18 with HTTP; Tue, 22 May 2012 04:20:43 -0700 (PDT)
From: =?UTF-8?B?UGF3ZcWCIEhhamRhbiwgSnIu?= <phajdan...@chromium.org>
Date: Tue, 22 May 2012 13:20:43 +0200
Message-ID: <CAATLsPa+ePzObphu_Kh-y3h_EWTDohgHgiCb-eagHSdoOuZ...@mail.gmail.com>
Subject: nacl toolchain in two directories?
To: chromium-dev <chromium-...@chromium.org>
Content-Type: multipart/alternative; boundary=20cf303dd808d3c41804c09e36b9

--20cf303dd808d3c41804c09e36b9
Content-Type: text/plain; charset=ISO-8859-1

It seems there is a recent change that puts nacl toolchain under
both native_client/toolchain/linux_x86_newlib and
native_client/toolchain/linux_x86. See Gentoo bug
https://bugs.gentoo.org/show_bug.cgi?id=417019 .

Is that on purpose? What's the reason?

--20cf303dd808d3c41804c09e36b9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It seems there is a recent change that puts nacl toolchain under both=A0nat=
ive_client/toolchain/linux_x86_newlib and native_client/toolchain/linux_x86=
. See Gentoo bug=A0<a href=3D"https://bugs.gentoo.org/show_bug.cgi?id=3D417=
019">https://bugs.gentoo.org/show_bug.cgi?id=3D417019</a> .<div>

<br></div><div>Is that on purpose? What&#39;s the reason?</div>

--20cf303dd808d3c41804c09e36b9--