lirc autodetection fails on debian unstable with udev, after lirc install and reboot

[admin@…]

ok, at least here, on a debian unstable running udev, lirc created the lirc,
lircd and lircm devices on pack install. for some reason after reboot only the
lircd device appears but thats no problem to me because the lircd and lirc
clients I use, work fine just with it.

mplayer needed on autodetection the lirc device it seems (or sth similar,
dindn't check much) so it would ignore lirc on the system.

using --enable-lirc compiled it and worked fine.

[diego@…]

Does the /dev/lirc device exist? Is it readable? Do you have the LIRC
development packages installed?

[admin@…]

only the /dev/lircd device remains (not lirc or lircm) after a reboot and the
lircd daemon and a couple of lirc clients I use work fine with it. I have the
dev files and --enable-lirc compiles lirc support normally and the remote works
ok with mplayer.

[admin@…]

(In reply to comment #2)

only the /dev/lircd device remains (not lirc or lircm) after a reboot and the
lircd daemon and a couple of lirc clients I use work fine with it. I have the
dev files and --enable-lirc compiles lirc support normally and the remote works
ok with mplayer.

forgot to mention,
srw-rw-rw- 1 root root 0 2006-02-27 03:39 /dev/lircd

[Dominik 'Rathann' Mierzejewski]

I'm beginning to think it may be wrong to use device file existence checks in
any autodetection. Think: automated builds in a chroot.

[diego@…]

I have removed the check for the LIRC devices from the configure test.