On Wed, 21 Dec 2011, Andreas Tobler wrote:
> Andreas fixed the issue and committed a fix:
>
> http://gcc.gnu.org/ml/gcc-cvs/2011-12/msg00686.html
>
> After this commit I was able to succesfully bootstrap (r182546) on
> x86_64-unknown-freebsd10.0.
Yep, I am happy to confirm it also works on my te
On 20.12.11 23:35, Eric Botcazou wrote:
So, the patch causing this was reverted and bootstrap worked again(?),
and now it is broken again with the same failure mode:
cc1: error: unrecognized command line option "-Wno-narrowing"
Actually, not the same, now it is invoking system gcc instead of
> So, the patch causing this was reverted and bootstrap worked again(?),
> and now it is broken again with the same failure mode:
>
> cc1: error: unrecognized command line option "-Wno-narrowing"
>
> Actually, not the same, now it is invoking system gcc instead of
> system g++:
>
> gcc -I/scra
On Sun, 18 Dec 2011, Eric Botcazou wrote:
>> Here g++ is invoked without an absolute path, so if you have an older
>> version of g++ in your path that does not grok -Wno-narrowing yet that
>> will fail, won't it? I assume that's why only some like you and me are
>> seeing this, but not all of us.
> Here g++ is invoked without an absolute path, so if you have an older
> version of g++ in your path that does not grok -Wno-narrowing yet that
> will fail, won't it? I assume that's why only some like you and me are
> seeing this, but not all of us.
Yes, for some reason the base C++ compiler is
On Sat, 17 Dec 2011, Eric Botcazou wrote:
>> Putting into gcc/cp/config-lang.in is a layering violation, it's true. But
>> until there's another instance that needs handling, it seems premature to
>> build infrastructure to handle this. And it's only one line after all...
> I don't know exactly w
Richard Henderson writes:
> There's no "good" place for this. The description in Makefile.def that
> libitm uses c++ is only used insofar as the dependencies for libitm -- it's
> built after libstdc++ as the language support library. If we put this into
> the toplevel configure.ac directly,
On 12/17/2011 06:19 AM, Eric Botcazou wrote:
>> Putting into gcc/cp/config-lang.in is a layering violation, it's true. But
>> until there's another instance that needs handling, it seems premature to
>> build infrastructure to handle this. And it's only one line after all...
>
> I don't know exa
On Sat, Dec 17, 2011 at 6:19 AM, Eric Botcazou wrote:
>> Putting into gcc/cp/config-lang.in is a layering violation, it's true. But
>> until there's another instance that needs handling, it seems premature to
>> build infrastructure to handle this. And it's only one line after all...
>
> I don't
> Putting into gcc/cp/config-lang.in is a layering violation, it's true. But
> until there's another instance that needs handling, it seems premature to
> build infrastructure to handle this. And it's only one line after all...
I don't know exactly why, but this breaks bootstrap on some machines
10 matches
Mail list logo
