Hi,
On Tue, Sep 30, 2003 at 12:27:29AM +0200, Eduard Bloch wrote:
> > > kdist_clean:
> > > $(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules clean
> >
> > Are those $(MFLAGS) really useful?
> > I thought they were not because $(MAKE) also had the flags, but I'm not
> > sure anymore...
>
>
#include
* Nicolas Boullis [Mon, Sep 29 2003, 11:42:59PM]:
> On Mon, Sep 29, 2003 at 01:43:05PM -0400, David Z Maze wrote:
>
> > I don't consider it a bug. I do think the kdist and kdist_image
> > targets should reinvoke make under $(ROOT_CMD), though, just to be
> > sure. The i2c-source debia
Hi,
On Mon, Sep 29, 2003 at 01:43:05PM -0400, David Z Maze wrote:
> I don't consider it a bug. I do think the kdist and kdist_image
> targets should reinvoke make under $(ROOT_CMD), though, just to be
> sure. The i2c-source debian/rules file has:
>
> kdist_image:
> $(ROOT_CMD) $(MAKE)
On 29 Sep 2003 15:31:42 +0200, Henning Makholm <[EMAIL PROTECTED]> said:
> Scripsit Manoj Srivastava <[EMAIL PROTECTED]>
>> He said use the kernel-headers package, not kernel-package. Any
>> debian packaged module shall work with something like:
>> ./debian/rules KVERS="2.4.21" KSRC="/usr/src/ke
Henning Makholm <[EMAIL PROTECTED]> writes:
> Scripsit Manoj Srivastava <[EMAIL PROTECTED]>
>
>> He said use the kernel-headers package, not
>> kernel-package. Any debian packaged module shall work with something
>> like:
>
>> ./debian/rules KVERS="2.4.21" KSRC="/usr/src/kernel-headers-2.4
Scripsit Manoj Srivastava <[EMAIL PROTECTED]>
> He said use the kernel-headers package, not
> kernel-package. Any debian packaged module shall work with something
> like:
> ./debian/rules KVERS="2.4.21" KSRC="/usr/src/kernel-headers-2.4.21"
> KPKG_DEST_DIR="../" KDREV="blah" kdist_image
On Tue, 23 Sep 2003 20:39:04 +0200, Manuel Bilderbeek <[EMAIL PROTECTED]> said:
> Hello, Kernel 2.4.22 got into testing, so I have to go to the
> procedure again.
>> #include
>> * Manuel Bilderbeek [Sun, Aug 24 2003, 04:32:45PM]:
>>
>>> The procedure I'm going through is as follows (being root
Hello,
Kernel 2.4.22 got into testing, so I have to go to the procedure again.
#include
* Manuel Bilderbeek [Sun, Aug 24 2003, 04:32:45PM]:
The procedure I'm going through is as follows (being root all the time)
1) install the kernel source for the kernel, e.g. kernel-source-2.4.21
2) go to /usr/s
#include
* Manoj Srivastava [Mon, Aug 25 2003, 03:50:33PM]:
Okay, I think I have found a solution for the people with different
points of view. First, let's summarize some.
> >> > This is my view: the kernel headers and the configuration used
> >> > when compiling a stock kernel are to be viewed
On Mon, 25 Aug 2003 20:26:29 +0200, horrorvacui <[EMAIL PROTECTED]> said:
> On Sun, 24 Aug 2003 19:50:18 -0500
> Manoj Srivastava <[EMAIL PROTECTED]> wrote:
>> On Sun, 24 Aug 2003 20:16:21 +0200, horrorvacui
>> <[EMAIL PROTECTED]> said:
>>
>> > This is my view: the kernel headers and the config
On Sun, 24 Aug 2003 19:50:18 -0500
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> On Sun, 24 Aug 2003 20:16:21 +0200, horrorvacui <[EMAIL PROTECTED]>
> said:
>
> > This is my view: the kernel headers and the configuration used when
> > compiling a stock kernel are to be viewed as an *integral par
Manuel Bilderbeek <[EMAIL PROTECTED]> writes:
> After having worked with Debian testing for about 2 years, I'm getting
> fed up with the seemingly unnecessarily complicated way of building
> kernel modules for the stock kernels.
> 1) install the kernel source for the kernel,
>e.g. kernel-sour
On Sun, 24 Aug 2003 20:16:21 +0200, horrorvacui <[EMAIL PROTECTED]> said:
> I don't. He certainly has a point, and I wanted to post a message
> about this, only he was faster. I recently installed debian for a
> friend, installed alsa and was completely helpless as to where to
> obtain them. I t
On Sun, 24 Aug 2003 18:02:32 +0200, Manuel Bilderbeek <[EMAIL PROTECTED]> said:
> At the time I still used it (again, one year ago or so), this didn't
> work out-of-the-box, because of the APPEND_TO_VERSION stuff. I see
> this has been fixed in the meantime, in step 4 of the installation
> instru
On Sun, 24 Aug 2003 17:16:25 +0200
Eduard Bloch <[EMAIL PROTECTED]> wrote:
> #include
> * Manuel Bilderbeek [Sun, Aug 24 2003, 04:32:45PM]:
>
> > The procedure I'm going through is as follows (being root all the
> > time)
> >
> > 1) install the kernel source for the kernel, e.g. kernel-source-2
2) go to /usr/src and tar xjvf kernel-source-2.4.21.tar.bz2
Why don't you use the kernel-headers packages and use them as partial
kernel source? They provide header files (including the complete kernel
version) and the .config that belongs to them.
Because for some of them it wasn't enough. So, to
#include
* Manuel Bilderbeek [Sun, Aug 24 2003, 04:32:45PM]:
> The procedure I'm going through is as follows (being root all the time)
>
> 1) install the kernel source for the kernel, e.g. kernel-source-2.4.21
>
> 2) go to /usr/src and tar xjvf kernel-source-2.4.21.tar.bz2
Why don't you use th
Hello,
After having worked with Debian testing for about 2 years, I'm getting
fed up with the seemingly unnecessarily complicated way of building
kernel modules for the stock kernels.
I'm talking about packages like lm-sensors-source, the nvidia kernel
modules (haven't done that in a year thoug
18 matches
Mail list logo
