[Speex-dev] error during make

[venkatram mustoor]

Hi All,

I am getting this error when i try to compile the "Linphone" package
by typing----- make.

please help me i am feeling very frustrated with this error pasdt from
7 days i am getting this error.

please help me.
speexec.c: In function `speex_ec_process':
speexec.c:112: `spx_int32_t' undeclared (first use in this function)
speexec.c:112: (Each undeclared identifier is reported only once
Hi All,

Please help me how to get rid of this error.

speexec.c:112: for each function it appears in.)
speexec.c:112: `noise' undeclared (first use in this function)
speexec.c:112: parse error before ')' token
cc1: warnings being treated as errors
speexec.c:133: warning: implicit declaration of function
`speex_echo_state_reset'
make[3]: *** [speexec.lo] Error 1
make[3]: Leaving directory
`/home/umesh/IPPHONE/linphone-1.5.1/mediastreamer2/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/umesh/IPPHONE/linphone-1.5.1/mediastreamer2/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/umesh/IPPHONE/linphone-1.5.1/mediastreamer2'
make: *** [all] Error 2


On 2/7/07, speex-dev-request at xiph.org <speex-dev-request at xiph.org> wrote:
> Send Speex-dev mailing list submissions to
> 	speex-dev at xiph.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.xiph.org/mailman/listinfo/speex-dev
> or, via email, send a message with subject or body 'help' to
> 	speex-dev-request at xiph.org
>
> You can reach the person managing the list at
> 	speex-dev-owner at xiph.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Speex-dev digest..."
>
>
> Today's Topics:
>
>    1. svn AGC (Alfredo Moreira)
>    2. Re: [xiph-rtp] Re: [Vorbis-dev] Proposal: An extension	to
>       rules all others (Silvia Pfeiffer)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 06 Feb 2007 18:43:47 +0100
> From: Alfredo Moreira <alfredo.moreira at neolinks.com>
> Subject: [Speex-dev] svn AGC
> To: speex-dev at xiph.org
> Message-ID: <45C8BE53.9070004 at neolinks.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi Jean Marc,
>
> I found that the AGC API and algorithm has changed in svn head trunk.
> Is it safe to use it? Or is it for testing purpose only?
> You also said that VAD in svn is broken in a previous post, is it
> related to the AGC change?
> or can we mix the old VAD algorithm with the new AGC safely?
>
> kind regards,
> fredo
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 7 Feb 2007 06:18:26 +1100
> From: "Silvia Pfeiffer" <silviapfeiffer1 at gmail.com>
> Subject: [Speex-dev] Re: [xiph-rtp] Re: [Vorbis-dev] Proposal: An
> 	extension	to rules all others
> To: "Tor-Einar Jarnbjo" <tor-einar at jarnbjo.name>
> Cc: advocacy at xiph.org, speex-dev at xiph.org, theora-dev at xiph.org,
> 	vorbis-dev at xiph.org, flac-dev at xiph.org, ogg-dev at xiph.org,
> 	xiph-rtp at xiph.org
> Message-ID:
> 	<2c0e02830702061118p4f4e2d02g21d376ef574d0d9f at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> An addition of the MIME type to the first Ogg page doesn't make much
> sense, since that Ogg page already belongs to one of the logical
> bitstreams in the stream.
>
> We had a long discussion about how to do this right when developing
> the Annodex format
> (http://annodex.net/TR/draft-pfeiffer-annodex-02.txt), which has been
> built to provide this functionality and others.
>
> In the end, we defined what is now know as "skeleton"
> (http://wiki.xiph.org/index.php/Ogg_Skeleton) and as an additional
> logical bitstream at the beginning of an Ogg file that contains
> information o the other logical bitstreams inside the Ogg file.
>
> This is the only way to provide this information without breaking
> existing specifications.
>
> However, it requires that Ogg parsing software be adapted to also
> parse Skeleton.
>
> Some of the software has already been adapted for it - others hasn't.
>
> Silvia.
>
> On 1/17/07, Tor-Einar Jarnbjo <tor-einar at jarnbjo.name> wrote:
> > Aaron Colwell schrieb:
> >
> > > Media applications are able to deeply inspect the file if they really
> > > need to
> > > determine which codec it contains.
> > >
> > In case of Ogg, the application is unfortunately only able to determine
> > which codec(s) the Ogg file contains if detailed knowledge about the
> > codecs is known already by the Ogg parser. I think I already suggested
> > to e.g. add the stream's MIME type to the first Ogg page to make it
> > easier for players to cope with new codecs embedded in an Ogg file.
> >
> > Tor
> >
> > _______________________________________________
> > Vorbis-dev mailing list
> > Vorbis-dev at xiph.org
> > http://lists.xiph.org/mailman/listinfo/vorbis-dev
> >
>
>
> ------------------------------
>
> _______________________________________________
> Speex-dev mailing list
> Speex-dev at xiph.org
> http://lists.xiph.org/mailman/listinfo/speex-dev
>
>
> End of Speex-dev Digest, Vol 33, Issue 7
> ****************************************
>