On Sun, Nov 09, 2003 at 06:50:06PM +0100, Santiago Vila wrote:
> Do I need a cvs-hurd or a cvs-gnumach to compile it?

I don't think so.

> gcc-3.3 ../sysdeps/i386/setfpucw.c -c -std=gnu99 -O2 -Wall -Winline 
> -Wstrict-prototypes -Wwrite-strings -fstrict-aliasing -g -pipe 
> -Wno-parentheses -mpreferred-stack-boundary=4    -Wno-uninitialized 
> -D__NO_MATH_INLINES -D__LIBC_INTERNAL_MATH_INLINES -I../include -I. 
> -I/build/buildd/glibc-2.3.2.ds1/build-tree/hurd-i386-libc/math -I.. 
> -I../libio -I../hurd 
> -I/build/buildd/glibc-2.3.2.ds1/build-tree/hurd-i386-libc/hurd/ -I../mach 
> -I/build/buildd/glibc-2.3.2.ds1/build-tree/hurd-i386-libc/mach/ 
> -I/build/buildd/glibc-2.3.2.ds1/build-tree/hurd-i386-libc 
> -I../sysdeps/i386/elf -I../sysdeps/mach/hurd/i386 -I../sysdeps/mach/hurd 
> -I../sysdeps/gnu -I../sysdeps/unix/bsd/bsd4.4 -I../sysdeps/unix/mman 
> -I../sysdeps/mach/i386 -I../sysdeps/mach -I../sysdeps/i386/fpu 
> -I../sysdeps/i386 -I../sysdeps/wordsize-32 -I../sysdeps/ieee754/ldbl-96 
> -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/unix/bsd 
> -I../sysdeps/unix/common -I../sysdeps/unix/inet -I../sysdeps/unix 
> -I../sysdeps/posix -I../sysdeps/ieee754 -I../sysdeps/generic/elf 
> -I../sysdeps/generic  -D_LIBC_REENTRANT -include ../include/libc-symbols.h    
>    -o /build/buildd/glibc-2.3.2.ds1/build-tree/hurd-i386-libc/math/setfpucw.o 
> -MD -MP -MF 
> /build/buildd/glibc-2.3.2.ds1/build-tree/hurd-i386-libc/math/setfpucw.o.dt
> ../sysdeps/i386/setfpucw.c: In function `__setfpucw':
> ../sysdeps/i386/setfpucw.c:43: error: `HWCAP_I386_XMM' undeclared (first use 
> in this function)
> ../sysdeps/i386/setfpucw.c:43: error: (Each undeclared identifier is reported 
> only once
> ../sysdeps/i386/setfpucw.c:43: error: for each function it appears in.)

That one (and a couple of others) are fixed in CVS, thanks to ams.

I've got a dpatch for that one if you or Jeff are interested. But I
guess waiting for the next debian release with pulls from CVS will be
easier.


Michael


  • Re: glibc Michael Banck

Reply via email to