Re: FD_ZERO in lirc_client causing impossible constraint in 'asm'

[Jeff S. <jef...@gm...>]

never mind I think I see the problem Its a ulibc with arm problem

On 5/15/07, Jeff Sadowski <jef...@gm...> wrote:
> after all the includes I included this
>
> #define __KERNEL__
> #include <asm-arm/posix_types.h>
>
> so that I know I have the right definitions for FD_ZERO
>
> which actually took me further
>
> now I get another error that im afraid im stuck on
>
> lirc_client.c: In function 'lirc_read_string':
> lirc_client.c:1891: error: 'fd_set' has no member named 'fds_bits'
> make[2]: *** [lirc_client.lo] Error 1
> make[2]: Leaving directory
> `/root/gumstix-verdex-buildroot-1370/build_arm_nofpu/lirc-0.8.1/tools'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory
> `/root/gumstix-verdex-buildroot-1370/build_arm_nofpu/lirc-0.8.1'
> make: *** [all] Error 2
>
>
> looking into it I'm afraid that the fd_set in uclib doesn't have a
> full set of things I need for lirc_client is there a way around this
>
> On 5/15/07, Jeff Sadowski <jef...@gm...> wrote:
> > I have learned that this is a problem with my kernel header.
> >
> > here is the relevent kernel header
> >
> > #undef  __FD_ZERO
> > #define __FD_ZERO(fdsetp) \
> >                (memset (fdsetp, 0, sizeof (*(fd_set *)(fdsetp))))
> >
> > #endif
> >
> > This is on an arm architecture.
> >
> > has anyone else ran into this when cross compiling?
> >
> > Is there a way to fix it?
> >
> > here is the error I get when trying to compile
> >
> > lirc_client.c: In function 'lirc_send_command':
> > lirc_client.c:1887: error: impossible constraint in 'asm'
> > make[2]: *** [lirc_client.lo] Error 1
> > make[2]: Leaving directory
> > `/root/gumstix-verdex-buildroot-1370/build_arm_nofpu/lirc-0.8.1/tools'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory
> > `/root/gumstix-verdex-buildroot-1370/build_arm_nofpu/lirc-0.8.1'
> > make: *** [all] Error 2
> >
> >
> > line 1887 has
> >
> > FD_ZERO(&fds);
> >
> > fds was created with
> >
> > fd_set fds;
> >
> > If someone has fixed this I would love to here how. I'll look into it some more
> > hopefully I'll find a solution.
> >
>