[MPlayer-users] lirc issue

[Banu Cosmin]

problem solved, it seemed to be from some wrong symlinks

thanks anyway :)

On Monday 02 December 2002 12:24 am, Dominik Mierzejewski wrote:
> [Automatic answer: RTFM (read DOCS, FAQ), also read DOCS/bugreports.html]
>
> On Saturday, 30 November 2002, Banu Cosmin wrote:
> > 	Hi!
>
> Hi.
>
> > 	The past few days i have been trying to set up a proper rpm for
> > lirc-0.6.5.
> > 	I have downloaded a package from the net which contained all files
> > from the lirc package. I have split up the package in a lirc package and
> > two subpackages: lirc-devel and lirc-libs. You can see how they are
> > structured from the attached spec file. The thing is: mplayer requests
> > for building the presence of lirc-devel package, my question being: what
> > does mplayer need to be in that package for building and what does it
> > need in order to run with lirc enabled.
>
> Frankly: I'm not sure. I've never had access to any RC devices.
>
> > 	Don't get me wrong. I am not asking this in order to make a usable
> > lirc package, because the one i've build behaves gracefully. The thing is
> > that if i install lirc, lirc-libs and lirc-devel, when i rebuild the
> > mplayer-0.90-pre10 source package, passing it the "--with lirc" option, i
> > obtain the mplayer packages which installed do not "react" to the config
> > strings passed by lirc (i'm 100% sure that it's working ok). Running it
> > from the console i get "Setting up lirc support..." which tells me that
> > it's all ok... but nothing happens. I am also providing the .lircrc file,
> > just in case.
>
> I see that's the package from freshrpms.net. I've looked at it once and it
> seems to lack support for many devices. However, a full rpm build log would
> be useful for determining if the fault lies within my MPlayer RPM or in
> that lirc package.
>
> > 	btw: i use the serial lirc driver for homebrew receiver; i compile
> > mplayer with the default settings, passing it only the "--with lirc"
> > option (however, shouldn't mplayer detect it by default?).
>
> Nope. The other developers and I agreed on a certain set of features that
> are enabled. The rest is not included to limit the number of package
> dependencies until mplayer is more modular.