can`t build lirc-modules-source with kernel 2.6.15

Bug #5343 reported by Drolyk on 2005-12-03
This bug report is a duplicate of:  Bug #35456: UVF exception: lirc 0.7.1pre2 -> 0.8.0. Edit Remove
Affects Status Importance Assigned to Milestone
lirc (Ubuntu)

Bug Description

I`m using dapper and i`ve got a problem with lirc kernel modules. On my system I`ve got linux-headers-2.6.15-6-686 installed. Steps to reproduce:

apt-get update
apt-get install linux-headers-2.6.15-6-686 lirc-modules-source
cd /usr/src
rm -rf modules
tar xzf lirc-modules.tar.gz
cd linux-headers-2.6.15-6-686
make-kpkg modules_image

Drolyk (drolyk) wrote :
Download full text (11.6 KiB)

Here is build log:
                               ARCH=i386 prepare
make[1]: Entering directory `/usr/src/linux-headers-2.6.15-6-686'
  CHK include/linux/version.h
  SPLIT include/linux/autoconf.h -> include/config/*
make[1]: Leaving directory `/usr/src/linux-headers-2.6.15-6-686'
echo done > stamp-kernel-configure
echo done > stamp-configure
for module in /usr/src/modules/lirc ; do \
          if test -d $module; then \
    (cd $module; \
              if ./debian/rules KVERS="2.6.15-rc3-ubuntu1" KSRC="/usr/src/linux-headers-2.6.15-6-686" \
                             KMAINT="Unknown Kernel Package Maintainer" <email address hidden>" \
                             KPKG_DEST_DIR="/usr/src/linux-headers-2.6.15-6-686/.." \
                             KPKG_MAINTAINER="Unknown Kernel Package Maintainer" \
                             KPKG_EXTRAV_ARG="" \
                             ARCH="i386" \
                             KDREV="10.00.Custom" kdist_image; then \
                  echo "Module $module processed fine"; \
              else \
                   echo "Module $module failed."; \
                   if [ "X" != "X" ]; then \
                      echo "Perhaps $module does not understand --rootcmd?"; \
                      echo "If you see messages that indicate that it is not"; \
                      echo "in fact being built as root, please file a bug "; \
                      echo "against $module."; \
                   fi; \
                   echo "Hit return to Continue"; \
         read ans; \
              fi; \
     ); \
  else \
               echo "Module $module does not exist"; \
               echo "Hit return to Continue?"; \
  fi; \
make[1]: Entering directory `/usr/src/modules/lirc'
sed -e "s!\$KVERS!2.6.15-rc3-ubuntu1!g; s!\$KSRC!/usr/src/linux-headers-2.6.15-6-686!; s!\$KARCH!i386!; s!\$KEMAIL!<email address hidden>!; s!\$KMAINT!Unknown Kernel Package Maintainer!; s!\$KDREV!10.00.Custom!; s!\$DEBDATE!Сбт, 03 Дек 2005 19:58:45 +0300!" debian/ > debian/control
# Add here commands to configure the package.
touch configure-stamp
# Add here commands to compile the package.
/usr/bin/make debconf
make[2]: Entering directory `/usr/src/modules/lirc'
mkdir modules
/usr/bin/make -e -C drivers SUBDIRS="lirc_dev"
make[3]: Entering directory `/usr/src/modules/lirc/drivers'
Making all in lirc_dev
make[4]: Entering directory `/usr/src/modules/lirc/drivers/lirc_dev'
mv Makefile Makefile.automake
cp ../Makefile.kernel Makefile
/usr/bin/make -C /usr...

Drolyk (drolyk) on 2005-12-03
Changed in lirc:
assignee: nobody → motu
Chuck Short (zulcss) wrote :

The reason why the lirc-modules-source fails to build is because the API for sysfs has changed. I am looking into making a patch.

Loic Pefferkorn (loic) wrote :

I have this error too, and it's listed on Debian BTS

Changed in lirc:
status: Unconfirmed → Confirmed
Dan (danser) wrote :

FWIW, lirc-0.8.0rc3 builds perfectly against the Dapper kernel for me.

Yann Rouillard (yann-pleiades) wrote :

I reproduced this problem on an uptodate dapper

Reinhard Tartler (siretart) wrote :

please check with amaya, otherwise free to upload

Changed in lirc:
status: Confirmed → Needs Info
Daniel T Chen (crimsun) wrote :

In lieu of 0.8.0, is 0.7.2-2 (fakesync if necessary) usable?

Yann Rouillard (yann-pleiades) wrote :

0.8.0 solves compilation problems with kernel >= 2.6.12.

Maybe this can be easily fixed by backporting modifications from 0.8.0 but I found easier to upgrade to 0.8.0.

Jaap Haitsma (jaap) wrote :

In Gentoo the bug is solved

The way to do it was just going to version 0.8.0

Any change there will be deb package for that version anytime soon

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.