Subject: Re: [ecasound] GCC 3.2
From: Michael Carmack (karmak_AT_karmak.org)
Date: Thu Sep 19 2002 - 11:31:40 EEST
On Thu, Sep 19, 2002 at 09:42:38AM +0300, Kai Vehmanen wrote:
> On Thu, 19 Sep 2002, Michael Carmack wrote:
>
> > Does ecasound compile under GCC 3.2?
>
> Yes. I'm already using 3.2 as my main compiler.
>
> > I've attempted to do so, but the configure script looks for map.h, which
> > apparently has been moved to ${gccdir}/include/c++/3.2/backward/map.h as
> > of 3.2. I'm assuming this means map.h is deprecated and only provided for
> > backwards compatibility.
>
> There's a known bug with the configure script that comes with all
> released versions of 2.0.x ecasound (and older) which causes a failed
> check for map.h with gcc-3.2. The 2.0.x CVS-tree (2.0.5) has a fix for
> this as do all versions of 2.1devX.
>
> As a quick fix, just replace 'map.h' with 'map' in configure.in, run
> autoconf and then re-run configure.
A little tricky, but I was able to get this to work with autoconf/2.52
and automake/1.4p5. I didn't have success with various combinations of
autoconf/2.53, automake/1.5, and automake/1.6.3. One error in particular
that kept coming up with autoconf/2.53 was:
./configure: line 5861: syntax error near unexpected token `yes:no'
./configure: line 5861: ` yes:no'
Also, automake/1.5 and automake/1.6.3 seemed to have trouble with
kvutils/Makefile.am, complaining about DIST_COMMON using '=' instead
of '+=' (automake/1.4p5 took it though).
I also found that I had to change "CXXFLAGS+=" to "CXXFLAGS = @CXXFLAGS@"
at the top of kvutils/Makefile.am to stop automake from complaining.
Don't know if any of that info is useful... Ecasound did eventually
compile, so I'm satisfied :)
m.
This archive was generated by hypermail 2b28 : Thu Sep 19 2002 - 11:30:47 EEST