José Matos <[EMAIL PROTECTED]> writes:
| On Friday 18 August 2006 00:32, José Matos wrote:
| > I am waiting for the compilation to finish in the desktop, that presented
| > the same problem as the laptop...
|
| Yes, the compilation works if I disable pch.
|
| What is wrong with it?
gcc
-
On Friday 18 August 2006 00:32, José Matos wrote:
> I am waiting for the compilation to finish in the desktop, that presented
> the same problem as the laptop...
Yes, the compilation works if I disable pch.
What is wrong with it?
--
José Abílio
On Thursday 17 August 2006 12:30, Lars Gullik Bjønnes wrote:
> I am also on FC5 and I never get them...
Do you use pre-compiled headers?
I suspect that it should be something related since it touches most of the
files. The first where it claims that the anonymous namespace was defined is
Bi
On Thursday 17 August 2006 13:22, Jean-Marc Lasgouttes wrote:
> concept checks?
I disable them with the same result.
> JMarc
--
José Abílio
> "José" == José Matos <[EMAIL PROTECTED]> writes:
José> On Thursday 17 August 2006 12:30, Lars Gullik Bjønnes wrote:
>> I am also on FC5 and I never get them...
José> I have used a fresh checkout to avoid any possible
José> contamination...
José> The results are those you see. Could it
On Thursday 17 August 2006 12:30, Lars Gullik Bjønnes wrote:
> I am also on FC5 and I never get them...
I have used a fresh checkout to avoid any possible contamination...
The results are those you see. Could it be some package I (don't) have
installed and that configure does not react accor
José Matos <[EMAIL PROTECTED]> writes:
| On Thursday 17 August 2006 09:34, Hartmut Haase wrote:
| > In similar messages the _9 ist another number.
| > With suse92 it works.
|
| I am using FC5, I get all those warnings for multiple definition of
| `(anonymous namespace)::_
|
| This happens f
On Thursday 17 August 2006 09:34, Hartmut Haase wrote:
> In similar messages the _9 ist another number.
> With suse92 it works.
I am using FC5, I get all those warnings for multiple definition of
`(anonymous namespace)::_
This happens for every frontend.
So in the last month I have been u
