[Lame-dev] Re: Please report configure problems (autoconf update)

[Mark T. <mt...@mp...>]

I get exactly the same error on my RedHat 6.1 system
(gcc upgraded to gcc 2.95).  gcc complains about uint8_t, but
./configure thinks gcc has it.  

This older verison seems to work for me:

cvs update -D "2002-05-27 12:00" configure

Mark



> 
> > Hi,
> >
> > I've updated configure.in to autoconf 2.53. Please test if there's
> 
> I checked out a fresh copy on Mac OS X 10.1.4. ./configure completes 
> without problem, but then during compilation the types uint8_t, uint16_t 
> and uint32_t turn out to be undefined:
> 
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I. -I../libmp3lame -I.. -O3 
> -fomit-frame-pointer -ffast-math -funroll-loops -Wall -pipe -fno-common -c 
> interface.c -Wp,-MD,.deps/interface.TPlo -o interface.o
> ../libmp3lame/VbrTag.h:75: undefined type, found `uint8_t'
> ../libmp3lame/VbrTag.h:75: undefined type, found `uint32_t'
> ../libmp3lame/VbrTag.h:75: undefined type, found `uint16_t'
> ../libmp3lame/VbrTag.h:78: undefined type, found `uint16_t'
> cpp-precomp: warning: errors during smart preprocessing, retrying in basic 
> mode
> In file included from interface.c:14:
> ../libmp3lame/VbrTag.h:75: parse error before `uint8_t'
> ../libmp3lame/VbrTag.h:78: parse error before `*'
> 
> 
> ./configure erroneously thinks that
> 
> checking for uint8_t... yes
> checking for int8_t... yes
> checking for uint16_t... yes
> checking for int16_t... yes
> checking for uint32_t... yes
> checking for int32_t... yes
> checking for uint64_t... yes
> checking for int64_t... yes
> 
> 
> An older ./configure script resulted in the following, with no compilation 
> errors:
> 
> checking for uint8_t... no
> checking for int8_t... yes
> checking for uint16_t... no
> checking for int16_t... yes
> checking for uint32_t... no
> checking for int32_t... yes
> checking for uint64_t... no
> checking for int64_t... yes
>