[x264-devel] gcc 3.2 compilation error

Guillaume POIRIER poirierg at gmail.com
Tue Aug 21 21:35:01 CEST 2007


Hi,

On 8/21/07, David Liontooth <liontooth at cogweb.net> wrote:
> David Liontooth wrote:
> > On a beowulf cluster with gcc 3.2 I get this error:
> >
> > liontooth at beowulf:~/software/tarballs/x264-snapshot-20070820-2245$

> > gcc -O4 -ffast-math  -Wall -I. -DHAVE_MALLOC_H -DHAVE_MMX -DARCH_X86
> > -DSYS_LINUX -DHAVE_PTHREAD -s -fomit-frame-pointer   -c -o common/dct.o
> > common/dct.c
> > gcc -O4 -ffast-math  -Wall -I. -DHAVE_MALLOC_H -DHAVE_MMX -DARCH_X86
> > -DSYS_LINUX -DHAVE_PTHREAD -s -fomit-frame-pointer   -c -o common/cpu.o
> > common/cpu.c
> > common/cpu.c: In function `x264_cpu_num_processors':
> > common/cpu.c:212: `cpu_set_t' undeclared (first use in this function)
> > common/cpu.c:212: (Each undeclared identifier is reported only once
> > common/cpu.c:212: for each function it appears in.)
> > common/cpu.c:212: parse error before "p_aff"
> > common/cpu.c:213: `p_aff' undeclared (first use in this function)
> > make: *** [common/cpu.o] Error 1
> >
> > Is this just an effect of the ancient gcc?
> >
> If I use "./configure --disable-pthread" it compiles -- I had to use
> "disable" rather than just leave out "enable".
> I'd like to have pthreads, though.
> > Has anyone used x264 on a beowulf cluster?

I bet all you need to do is just use a reasonable up-to-date version
of lib pthreads

Guillaume
-- 
A soldier will fight long and hard for a bit of colored ribbon.
 -- Napoleon Bonaparte
_______________________________________________
x264-devel mailing list
x264-devel at videolan.org
http://mailman.videolan.org/listinfo/x264-devel


More information about the x264-devel mailing list