[cfe-dev] choosing the gcc toolchain

[Simon Atanasyan]

And one a couple of questions more. When you check the first patch the
target triple was mipsel-unknown-linux-gnu. When you check the last
patch the target triple is mips64el-unknown-linux-gnu. Do you use the
same clang command line options both time? Does the 4.7.2 toolchain
contain 64-bit support?

On Mon, Mar 3, 2014 at 10:03 AM, Simon Atanasyan <simon at atanasyan.com> wrote:
> Could you:
> 1. Send the command line options used to run the clang
> 2. Run the following command and send its output:
> $ find /usr/lib -name crtbegin.o
>
> Thanks.
>
> On Mon, Mar 3, 2014 at 6:33 AM, Reed Kotler <rkotler at mips.com> wrote:
>> With this latest patch I'm seeing:
>>
>> rkotler at mipsswbrd006-le:~/caviumnativellvm/build$
>> ./Release+Asserts/bin/clang++ -v
>> clang version 3.5 (gitosis at dmz-portal.mips.com:clang.git
>> f4481e0e412e3f817e65d5ce1c835381dc7a7773)
>> (gitosis at dmz-portal.mips.com:llvm.git
>> 18fe44cb057e4b11533bd3f814b96fdca724baf0)
>> Target: mips64el-unknown-linux-gnu
>>
>> Thread model: posix
>> Found candidate GCC installation: /usr/lib/gcc/mipsel-linux-gnu/4.4
>> Found candidate GCC installation: /usr/lib/gcc/mipsel-linux-gnu/4.4.6
>> Found candidate GCC installation: /usr/lib/gcc/mipsel-linux-gnu/4.4.7
>> Found candidate GCC installation: /usr/lib/gcc/mipsel-linux-gnu/4.6
>> Found candidate GCC installation: /usr/lib/gcc/mipsel-linux-gnu/4.6.3
>> Found candidate GCC installation: /usr/lib/gcc/mipsel-linux-gnu/4.7
>> Found candidate GCC installation: /usr/lib/gcc/mipsel-linux-gnu/4.7.2
>> Selected GCC installation: /usr/lib/gcc/mipsel-linux-gnu/4.6
>> Candidate multilib: .;@m32
>> Candidate multilib: 64;@m64
>> Candidate multilib: n32;@mabi=n32
>> Selected multilib: 64;@m64
>> rkotler at mipsswbrd006-le:~/caviumnativellvm/build$
>>
>> The day before I was getting 4.7
>
> --
> Simon Atanasyan



-- 
Simon Atanasyan