| Summary: | app-misc/lirc-0.8.5 fails to build ( ftdi.h: No such file or directory ) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | DEMAINE Benoît-Pierre, aka DoubleHP <dhp_gentoo> |
| Component: | Current packages | Assignee: | Television related Applications in Gentoo's Portage <media-tv> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | fauli |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
/var/log/portage/app-misc:lirc-0.8.5:20090705-005753.log
/tmp/emerge--info build.log emerge--info |
||
|
Description
DEMAINE Benoît-Pierre, aka DoubleHP
2009-07-05 01:03:56 UTC
Created attachment 196697 [details]
/var/log/portage/app-misc:lirc-0.8.5:20090705-005753.log
Created attachment 196699 [details]
/tmp/emerge--info
Apparently the previous solution isn't working for you, since you're using the ebuild that includes bug 271482 fix -- so assigning to maintainers to take another look. Does your problem go away when you install dev-embedded/libftdi? Fixed in 0.8.6 by upstream, and fixed 0.8.5 by sping and me. Not fixed at all !!! x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -march=athlon64 -pipe -MT hw_ea65.o -MD -MP -MF .deps/hw_ea65.Tpo -c -o hw_ea65.o hw_ea65.c mv -f .deps/hw_ea65.Tpo .deps/hw_ea65.Po x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -O2 -march=athlon64 -pipe -MT hw_ftdi.o -MD -MP -MF .deps/hw_ftdi.Tpo -c -o hw_ftdi.o hw_ftdi.c hw_ftdi.c:54:18: error: ftdi.h: No such file or directory hw_ftdi.c: In function 'parsesamples': hw_ftdi.c:101: warning: ignoring return value of 'write', declared with attribute warn_unused_result Of course, emerge -v1 libftdi helps a lot ... Created attachment 216805 [details]
build.log
Created attachment 216806 [details]
emerge--info
(In reply to comment #5) > Fixed in 0.8.6 by upstream, and fixed 0.8.5 by sping and me. > uranus ~ # ls -lha /usr/portage/app-misc/lirc/lirc-0.8.5.ebuild -rw-r--r-- 1 portage portage 9.2K Oct 6 23:36 /usr/portage/app-misc/lirc/lirc-0.8.5.ebuild uranus ~ # Did you really do anything ? this ebuild seems to have changed 3 days after your comment, but does not have any "revision", and, does not really fix the bug: lirc does not depend on libftdi, and this is still a problem. And as long as 0.8.6 is not stable, whatever upstream could have done ... The question is: why have I be the only one having this bug in 3 months ? I'm experiencing this as well: make[3]: Entering directory `/var/tmp/portage/app-misc/lirc-0.8.5/work/lirc-0.8.5/daemons' i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -O3 -march=k8 -pipe -fomit-frame-pointer -msse -msse2 -msse3 -m3dnow -mmmx -MT hw-types.o -MD -MP -MF .deps/hw-types.Tpo -c -o hw-types.o hw-types.c mv -f .deps/hw-types.Tpo .deps/hw-types.Po i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -O3 -march=k8 -pipe -fomit-frame-pointer -msse -msse2 -msse3 -m3dnow -mmmx -MT ir_remote.o -MD -MP -MF .deps/ir_remote.Tpo -c -o ir_remote.o ir_remote.c mv -f .deps/ir_remote.Tpo .deps/ir_remote.Po i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -O3 -march=k8 -pipe -fomit-frame-pointer -msse -msse2 -msse3 -m3dnow -mmmx -MT release.o -MD -MP -MF .deps/release.Tpo -c -o release.o release.c mv -f .deps/release.Tpo .deps/release.Po i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I.. -O3 -march=k8 -pipe -fomit-frame-pointer -msse -msse2 -msse3 -m3dnow -mmmx -MT hw_ftdi.o -MD -MP -MF .deps/hw_ftdi.Tpo -c -o hw_ftdi.o hw_ftdi.c hw_ftdi.c:54:18: error: ftdi.h: No such file or directory So I'd say you're not the only one. If you have ftdi, usbirboy, userspace or all in your LIRC_DEVICES the ebuild pulls in dev-embedded/libftdi. So I don't understand where your problem is originated. David, are you still having this problem ? If yes, please don't fix it manually; my box is fixed and i can't repro; but if you can repro, we can try tracking the problem: emerge -vp lirc and let us see if you have LIRC flags, and if the ebuilds really brings dev-embedded/libftdi in for you. if dev-embedded/libftdi does not come in, check to see if it is in already or not: emerge -vp dev-embedded/libftdi equery d dev-embedded/libftdi If it is not in yet, we need to find why. What's your portage version ? How many changes did you do in /etc/portage ? David: of course we need your emerge --info |