[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gcc 3.0 trouble

From: Jan Nieuwenhuizen
Subject: Re: gcc 3.0 trouble
Date: 10 Aug 2001 11:22:55 +0200
User-agent: Gnus/5.090003 (Oort Gnus v0.03) Emacs/20.7

"Tom Cato Amundsen" <address@hidden> writes:

> I still can't get gcc 3.0 compile lilypond. It fails on the first
> c++ file.
> I run debian unstable with both g++ 2.95 and 3.0.1 installed,
> and I had the same problems with 3.0 some weeks ago. I guess there
> are some package I have missed.

It looks like some kind of installation or configuration problem, it
works fine here, on Debian/powerpc.

> Beginning of error message:
> In file included from /usr/include/g++-v3/bits/fpos.h:40,
>                  from /usr/include/g++-v3/bits/std_iosfwd.h:41,
>                  from /usr/include/g++-v3/bits/std_ios.h:39,
>                  from /usr/include/g++-v3/bits/std_ostream.h:39,
>                  from /usr/include/g++-v3/bits/std_iostream.h:40,
>                  from /usr/include/g++-v3/backward/iostream.h:32,
>                  from include/string.hh:13,
>                  from include/file-path.hh:12,
>                  from
> /usr/include/g++-v3/bits/std_cwchar.h:59: `mbstate_t' not declared

I looked into this, and mbstate_t is usually defined in wchar.h.  If
it's not, it should get defined in std_cwchar.h, just before your
error.  It looks like somehow, the #define's that guide this are

First, get this to compile:

    #include <iostream.h>
    main ()
            cout << "Hello world\n";
            return 0;

You can just edit /usr/include/g++-v3/bits/std_cwchar.h, and add some
#error directives to see what's #define'd and what not.  Also
/usr/include/g++-v3/<arch>-<os>/bits/c++config.h might be worth
looking at.


Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter       |

reply via email to

[Prev in Thread] Current Thread [Next in Thread]