This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Don't bootstrap libcc1


Dominique,
    That is curious. I wouldn't have thought that the compiler
selection would have had such a radical effect on the linkage flags
emitted for the build directories.
              Jack


On Sat, Nov 8, 2014 at 4:59 PM, Dominique d'HumiÃres <dominiq@lps.ens.fr> wrote:
>
>> Le 8 nov. 2014 Ã 22:55, Jack Howarth <howarth.at.gcc@gmail.com> a Ãcrit :
>>
>> Iain,
>>     Any idea why this isn't failing universally? On all of the
>> machines tested here with 'make bootstrap', the linkage of libcc1.so
>> finds
>> the necessary libstdc++ from the set of flags...
>>
>> -L/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/x86_64-apple-darwin13.4.0/libstdc++-v3/src
>> -L/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/x86_64-apple-darwin13.4.0/libstdc++-v3/src/.libs
>> -L/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/x86_64-apple-darwin13.4.0/libstdc++-v3/libsupc++/.libs
>>
>> as I posted earlier in this thread. Why wouldn't Dominique be getting
>> those emitted in his build and shouldn't they suffice?
>>          Jack
>
> Because you bootstrap with clang (I confirm it) while I am bootstrapping with gcc 4.9 for Ada.
>
> Dominique
>
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]