On Wednesday 27 September 2006 16:20, Hugo Vanwoerkom wrote:
> David Baron wrote:
> > Manually putting in the symlink worked. 2.6.18 is up and running.
> > Easily build the kqemu and, using m-a all the other added kernel models.
> > And yes, Nvidia's installer CAN be easily used with multiple kerne
David Baron wrote:
Manually putting in the symlink worked. 2.6.18 is up and running.
Easily build the kqemu and, using m-a all the other added kernel models.
And yes, Nvidia's installer CAN be easily used with multiple kernels and even
cross-compile (read their "advanced" options).
I'll keep 2
Manually putting in the symlink worked. 2.6.18 is up and running.
Easily build the kqemu and, using m-a all the other added kernel models.
And yes, Nvidia's installer CAN be easily used with multiple kernels and even
cross-compile (read their "advanced" options).
I'll keep 2.6.17 around for a few
David Baron wrote, On 2006-09-26 23:42:
On Tuesday 26 September 2006 02:54, Arthur Marsh wrote:
Hugo Vanwoerkom wrote, On 2006-09-26 03:49:
David Baron wrote:
I recall others have had a problem with this as well. Looks for the
asm/socket.h file.
This is very often a problem on a clean(ed) bui
On Tuesday 26 September 2006 17:47, Arthur Marsh wrote:
> David Baron wrote, On 2006-09-26 23:42:
> > On Tuesday 26 September 2006 02:54, Arthur Marsh wrote:
> >> Hugo Vanwoerkom wrote, On 2006-09-26 03:49:
> >>> David Baron wrote:
> I recall others have had a problem with this as well. Looks
On Tuesday 26 September 2006 02:54, Arthur Marsh wrote:
> Hugo Vanwoerkom wrote, On 2006-09-26 03:49:
> > David Baron wrote:
> >> I recall others have had a problem with this as well. Looks for the
> >> asm/socket.h file.
> >>
> >> This is very often a problem on a clean(ed) build, usually solved b
Hugo Vanwoerkom wrote, On 2006-09-26 03:49:
David Baron wrote:
I recall others have had a problem with this as well. Looks for the
asm/socket.h file.
This is very often a problem on a clean(ed) build, usually solved by
running a make until c files are actually being compiled and then
stoppin
David Baron wrote:
I recall others have had a problem with this as well. Looks for the
asm/socket.h file.
This is very often a problem on a clean(ed) build, usually solved by running a
make until c files are actually being compiled and then stopping it. Then one
could go on with whatever make
Hi,
As other people have already mentioned, make-kpkg clean is the
answer (it removes the stamp-* files too). I'd suggest that a perusal
of /usr/doc/kernel-package/{Poblems,README}.gz before building the
kernel (the problems file mentions this, at least i the newer
versions of kernel-p
On Wed, 9 Jul 1997, Michael Bucciarelli wrote:
> The second time around I also did make clean after make deb.
> Sorry I left this out.
> -- Mike
>
>
> Mike Bucciarelli, N7CK
> [EMAIL PROTECTED]
>
>
> --
> TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
> [EMAIL PROTECTE
Hi,
It looks like you forgot to remove or touch the stamp-configure and
stamp-image files created by the make-kpkg script in /usr/src/linux.
Once you do that, you should be able to recompile without a problem.
Also, "make-kpkg clean" should do it.
J. Goldman
On Wed, 9 Jul 1997, Michael Bucciarel
At 12:08 AM 1/19/97 +0100, Thomas Baetzler wrote:
>Victor Torrico wrote:
>>
>> When making a kernel 2.0.27 I do the following:
>[clumsy procedure deleted]
>
>Actually, on Debian it´s so much nicer to install the kernel-package
>package.
>Then you cd to the linux source, "make mrproper" and "make c
Pete Templin wrote:
> Ah-hah! Finally, what seems to be a simple sequence of commands for
> building a new kernel. But what must I do to ensure that my old kernel
> will continue to work (with its modules), especially if lilo wants to
> complain that the new kernel is too large? I assume that c
Victor Torrico wrote:
>
> When making a kernel 2.0.27 I do the following:
[clumsy procedure deleted]
Actually, on Debian it´s so much nicer to install the kernel-package
package.
Then you cd to the linux source, "make mrproper" and "make config" just
once, and then you can always rebuild your ker
> "kooij" == J P D Kooij <[EMAIL PROTECTED]> writes:
kooij> Regarding compiling and installing new kernels,
kooij> I would like to know more about details of installing new
kooij> (and older) kernels and have an overview of the process as
kooij> well. IMHO this is something th
On Fri, 17 Jan 1997, David Wright wrote:
> Am I right in thinking that a module is a module is a module?
> In other words, is the sound.o module always the same even though
> different base addresses/IRQs etc. were configured?
Nope. Each time you compile it, differences do occur. You can USE s
>
> On Fri, 17 Jan 1997, Victor Torrico wrote:
>
> > When making a kernel 2.0.27 I do the following:
> >
> > make mrproper
> > make config
> > make dep
> > make clean
> > make zImage
> > make modules
> > make modules_install
> > make install
> >
> > The "make install" is not documented in the "
On Fri, 17 Jan 1997, Martin Konold wrote:
> Every kernel release gets its own direcory in /etc/modules/
> So no need to backup the modules.
> The new directory gets created with
> make modules_install
Am I right in thinking that a module is a module is a module?
In other words, is the sound.o mo
Regarding compiling and installing new kernels,
On 17 Jan 1997, Guy Maor wrote:
> Victor Torrico <[EMAIL PROTECTED]> writes:
>
> > What exactly does "make install" do?
>
> See installkernel(8) and mkboot(8).
Hey, this is not a very elaborate answer.
I would like to know more about details o
On Fri, 17 Jan 1997, Pete Templin wrote:
Hi there,
> Ah-hah! Finally, what seems to be a simple sequence of commands for
> building a new kernel. But what must I do to ensure that my old kernel
> will continue to work (with its modules), especially if lilo wants to
> complain that the new kernel
Victor Torrico <[EMAIL PROTECTED]> writes:
> What exactly does "make install" do?
See installkernel(8) and mkboot(8).
Guy
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
On Fri, 17 Jan 1997, Victor Torrico wrote:
> When making a kernel 2.0.27 I do the following:
>
> make mrproper
> make config
> make dep
> make clean
> make zImage
> make modules
> make modules_install
> make install
>
> The "make install" is not documented in the "/usr/src/linux" directory
> as
22 matches
Mail list logo
