Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 71797 - lirc-0.7.0 emerge results in non-working lirc_serial driver
Summary: lirc-0.7.0 emerge results in non-working lirc_serial driver
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal
Assignee: Heinrich Wendel (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-19 14:47 UTC by Curtis Stanford
Modified: 2004-11-29 04:50 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Curtis Stanford 2004-11-19 14:47:45 UTC
After emerging lirc-0.7.0 using LIRC_OPTS="--with-driver=serial --with-port=0x2f8 --with-irq=3" and kernel gentoo-dev-sources-2.6.9-r4, the lirc_driver doesn't load. I've tracked this down to the fact that the config.h file at the top level of the lirc build directory contains parameters with quotes around them that shouldn't be there. For example, the #define LIRC_PORT "0x2f8" should read #define LIRC_PORT 0x2f8. If I stop the ebuild after configuration and remove the quotes and resume the ebuild, the driver works fine. Otherwise the LIRC_PORT parameter becomes a very large number instead of 2f8 like it should be. Not sure yet why this is happening but I got it working using the above technique. The parameters that need quotes removed are: LIRC_MAJOR, LIRC_IRQ, LIRC_PORT and LIRC_TIMER.

I know all about the conflict with the kernel serial driver and that's not the problem. I've been using the lirc-0.7.0-pre versions for quite a while with no problem until now.

Reproducible: Always
Steps to Reproduce:
1. emerge lirc-0.7.0
2. try to modprobe lirc_serial

Actual Results:  
Doesn't load with misleading message about serial port being in use.

Expected Results:  
module should have loaded successfully

Portage 2.0.51-r3 (default-linux/x86/2004.0, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.9-gentoo-r4 
i686)
===============================================================
==
System uname: 2.6.9-gentoo-r4 i686 VIA Nehemiah
Gentoo Base System version 1.6.6
Autoconf: sys-devel/autoconf-2.59-r5
Automake: sys-devel/automake-1.8.5-r1
Binutils: sys-devel/binutils-2.15.92.0.2-r1
Headers:  sys-kernel/linux26-headers-2.6.8.1-r1
Libtools: sys-devel/libtool-1.5.2-r7
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-march=i686 -msse -mmmx -mfpmath=sse -Os -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/
qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=i686 -msse -mmmx -mfpmath=sse -Os -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="ftp://ftp.ussg.iu.edu/pub/linux/gentoo ftp://mirrors.tds.net/gentoo http://
mirrors.tds.net/gentoo http://adelie.polymtl.ca/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.ca.gentoo.org/gentoo-portage"
USE="X acpi alsa apm avi berkdb bitmap-fonts cga crypt cscope curl dvd encode f77 flac fortran gdbm 
gif gpm gtk2 imlib jpeg libg++ libwww mad mikmod mmx motif mpeg mysql ncurses nptl nptlonly 
oggvorbis opengl oss pam perl png python qt quicktime readline sdl slang spell sse ssl svga tcpd tiff 
truetype usb x86 xml2 xv zlib video_cards_cle266"
Comment 1 Olivier Crete (RETIRED) gentoo-dev 2004-11-19 15:29:38 UTC
lanius.. who is that heino@gentoo.org in the changelog? ;)
Comment 2 Jordan 2004-11-20 03:55:52 UTC
those quotes are added by lirc-0.7.0-configure.in.patch of which I was wondering what it's purpose was. Now I know...to break my lirc_serial! All jokes aside, simply commenting out the patch line in the ebuild fixes this. A tad bit easier then stopping the merge and hand editing out the lines the patch had caused to be added...
Comment 3 Curtis Stanford 2004-11-26 08:24:15 UTC
I can confirm that the configure.in.patch is the problem. Why the patch adds quotes around these numeric arguments is beyond me because it is fine without the patch.
Comment 4 Heinrich Wendel (RETIRED) gentoo-dev 2004-11-29 04:50:33 UTC
removed the patch.