Martin Lohmeier wrote:
> Confirmed!
Yes, I did a quick google search, but wanted to be sure. 4 eyes see more
than just two :)
--
.''`. sleep: command not found
: :' :
`. `'Proudly running Debian GNU/Linux (Sid 2.6.10 Ext3)
`- www.amayita.com www.malapecora.
Amaya wrote:
Now i am currently testing if $KSRC/makefile exists, which is a bit
lame. Your approach looks better, but in debian packaged kernels the
include/linux/version.v file does not exist, the one I can see is
Sorry, typo ;-) I meant version.h
include/linux/version.h. Can you confirm there is
Martin Lohmeier wrote:
> the problem is not that complicated. There is a simple
>
> if [ -f "$KSRC/Rules.make" ];then
No, I just uploaded and that test is gone.
> the automatic build works. I don know how other module-source packages
> check if the directory contain a valid kernel source, but
Justin Pryzby wrote:
I doubt that this is the problem, but /usr/src/linux should not be the
current kernel. I believe its supposed to be (if anything) the kernel
against which libc was compiled.
Hi Justin,
the problem is not that complicated. There is a simple
if [ -f "$KSRC/Rules.make" ];then
i
On Sun, Mar 27, 2005 at 01:12:38AM +0100, Martin Lohmeier wrote:
> Package: lirc-modules-source
> Version: 0.7.1pre2-3
> Severity: grave
> Justification: renders package unusable
>
> Hi,
>
> the packages does not automaticly build with linux 2.6.11
>
> I have the source of my current kernel in /
tags 301590 sid pending
priority 301590 important
thanks
I am downloading priority because the package builds fine with other
kernels Debian ships. See #294174 for the release manager explaining how
this kind of bug is not Release Critical.
--
.''`. sleep: command not found
:
Package: lirc-modules-source
Version: 0.7.1pre2-3
Severity: grave
Justification: renders package unusable
Hi,
the packages does not automaticly build with linux 2.6.11
I have the source of my current kernel in /usr/src/linux, but after
configuring lirc-modules-source, he complains
/usr/src/l
7 matches
Mail list logo
