On Fri, Oct 28, 2011 at 12:40 PM, Alex Ferrando wrote:
> I've rebuild llvm and clang using gcc 4.6.2 and then reinstalled
> vim-clang-complete. It seems to work.
>
> Now second question, why the fixed version as clang dep?
>
It requires a rebuild with every release of gcc because the gcc paths ch
[2011-10-28 12:40:38 +0200] Alex Ferrando:
> On 28/10/11 08:50, Gaetan Bisson wrote:
> >[2011-10-28 08:37:56 +0200] Alex Ferrando:
> >>So, my question now is if it is safe to rebuild clang without the
> >>fixed version dependencie on GCC and then upgrade. Would clang break
> >>if the GCC version is
On 28/10/11 08:50, Gaetan Bisson wrote:
[2011-10-28 08:37:56 +0200] Alex Ferrando:
So, my question now is if it is safe to rebuild clang without the
fixed version dependencie on GCC and then upgrade. Would clang break
if the GCC version is different from 4.6.1?
I wouldn't think it would. Try it
[2011-10-28 08:37:56 +0200] Alex Ferrando:
> So, my question now is if it is safe to rebuild clang without the
> fixed version dependencie on GCC and then upgrade. Would clang break
> if the GCC version is different from 4.6.1?
I wouldn't think it would. Try it out and let us know. :)
--
Gaetan
With the last push of GCC in testing, I have some kind of trouble to get
pacman to update it. It seems that clang, which I'm using fro
vim-clang-complete from AUR requires a fixed version of GCC ( and LLVM,
but this now is not the my main concern) which makes me impossible to
update GCC:
erro
5 matches
Mail list logo