G'day all,
I have had a very frustrating morning trying to compile a new 2.2.17
kernel from the tarball sources for my up-to-date woody machine.
I get a make error on make zImage and on make bzImage, but not on make
vmlinux.
I was tearing my hair out over thisuntil I read the list this
On Thu, Mar 25, 1999 at 06:22:41PM +1200, John Leget wrote:
> Running potato im coming up against the following with kernel 2.2.4
>
> acct.c: In function `sys_acct':
> acct.c:197: too few arguments to function `filp_close'
> acct.c:203: too few arguments to function `filp_close'
> make[2]: *** [ac
In foo.debian-user, you wrote:
> Running potato im coming up against the following with kernel 2.2.4
>
> acct.c: In function `sys_acct':
> acct.c:197: too few arguments to function `filp_close'
> acct.c:203: too few arguments to function `filp_close'
> make[2]: *** [acct.o] Error 1
> make[2]: Leav
Running potato im coming up against the following with kernel 2.2.4
acct.c: In function `sys_acct':
acct.c:197: too few arguments to function `filp_close'
acct.c:203: too few arguments to function `filp_close'
make[2]: *** [acct.o] Error 1
make[2]: Leaving directory `/usr/src/kernel-source-2.2.4/k
> Jesse Lee wrote:
>
> here are the erros I get when I am compiling my kernel.
>
> as86 -o -a [bootsect.o]
> bootsect.s
> make[1]: as86: command not found
> make[1]: *** [bootsect.o] error 127
>
I had the same problem the first time I tried to compile the kernel. You
just need to in
here are the erros I get when I am compiling my
kernel.
as86 -o -a [bootsect.o]
bootsect.s
make[1]: as86: command not found
make[1]: *** [bootsect.o] error 127
make [zimage] Error 2
then it stops and the zImage is not
created.
now I am running kernel 2.0.34
I have tried i
[EMAIL PROTECTED] (Chris Ulrich) writes:
| I just recently abandoned my own linux setup and installed debian (hamm).
| This is a pretty much stock setup -- the only thing un-debian I've done so
| far is change /bin/sh to point to pdksh, but that *shouldn't* be the problem
| because I've compil
On Tue, 28 Jul 1998, Chris Ulrich wrote:
:
: I just recently abandoned my own linux setup and installed debian (hamm).
: This is a pretty much stock setup -- the only thing un-debian I've done so
: far is change /bin/sh to point to pdksh, but that *shouldn't* be the problem
: because I've com
I just recently abandoned my own linux setup and installed debian (hamm).
This is a pretty much stock setup -- the only thing un-debian I've done so
far is change /bin/sh to point to pdksh, but that *shouldn't* be the problem
because I've compiled many kernels with my old setup where I didn't
9 matches
Mail list logo
