Thanks for the more detailed info, I found dialog and compiled /
installed. I removed my prior versions of lirc and lirc-kmdl, purged my
modprobe.conf of all references to the i2c driver and then rebooted.
When I ran through your howto steps I got stumped again in step 2 when I
select save config and run configure it soon halted on a c++ sanity
check. I have attached my config.log file to this message in addition to
the following screen output from configure.
setup.sh written by Karsten Scheibler, 1999-JUN-28
If you have problems or questions please consult the mailing list
Configuration: .setup.config, executable shell script: configure.sh
Starting the generated shell script which will call configure with the right
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking whether make sets $(MAKE)... (cached) yes
checking for mknod... /bin/mknod
checking for mkfifo... /usr/bin/mkfifo
checking for depmod... /sbin/depmod
checking for libusb-config... no
checking whether ln -s works... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... none
checking how to run the C++ preprocessor... /lib/cpp
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
Please read the documentation!!!
Any help that anyone can offer on this would be greatly appreciated.
Mark Weaver wrote:
> Tyler Bartel wrote:
>> I was following your instructions and hit a stumbling block at
>> ./configure I receive the error that Dialog cannot be found, I do not
>> seem to have that package installed not can I find it anywhere. I am
>> running FC4. I already have Lirc installed (from apt-get) and
>> functioning with the ir-receiver for my PVR-150 so I am wondering if
>> I can apply your patch to my existing install or if I need to remove
>> and rebuild from a patched source.
> This is just the setup script missing the GUI frontend program. There
> should be an RPM for that, seems to be called 'dialog' from googling a
> bit and is a standard RedHat package.
> It is probably best to remove the old lirc package and build my
> pre-patched version from source. You should make sure lirc_i2c and/or
> any reference in modules.conf is gone also as this has caused problems
> for other people in the past (check the comments underneath the
> article for more information). Do let me know if you need any more help.
>> Mark Weaver wrote:
>>> Olav Nyboe wrote:
>>>> I think this is the same guy:
>>> Yup that's me.
>>>> I have had some success following his instructions and using his
>>>> driver. Though I haven't been able to correctly change channels on
>>>> my set-top box yet.
>>>> I have only been able to set the channel for single digit channels
>>>> ( can't use any channel above 9).
>>>> But this depends on the box you attempt to control, I could change
>>>> to all channels on another set-top box, but this box didn't have
>>>> svideo output so I didn't want to use that.
>>> Have sent some responses to you on that now, although unfortunately
>>> they are not as helpful as I'd like.
>>> The driver basically just replays captures of what the Windows stuff
>>> does to the chip, so it's pretty limited in what it can support. If
>>> any brave soul can work out the format of the data blocks then we
>>> can probably get further than that. It is definitely structured as
>>> the windows software builds the data blocks rather than stores them
>>> all (although there are some big tables in there).
>>> As an aside, you might also want to look at
>>> if you have trouble with the remove stopping responding, this seems
>>> to have done the trick for a half-dozen people (including me to date).
>>> This SF.Net email is sponsored by the JBoss Inc.
>>> Get Certified Today * Register for a JBoss Training Course
>>> Free Certification Exam for All Training Attendees Through End of 2005
>>> Visit http://www.jboss.com/services/certification for more information
>> This SF.Net email is sponsored by the JBoss Inc.
>> Get Certified Today * Register for a JBoss Training Course
>> Free Certification Exam for All Training Attendees Through End of 2005
>> Visit http://www.jboss.com/services/certification for more information