Re: strange error compiling kernel 4.19.0-6-amd64

2019-09-30 Thread deloptes 
John Covici wrote:

> I am trying to do something very simple, with the config file supplied
> from Debian, I need to do a make bzImage and possible a make modules,
> how can dI do this?  Do I need to change the config in some way in
> order to do this?

be patient and start reading - free means free to understand and this means
read a lot.

see my other answer below

Re: strange error compiling kernel 4.19.0-6-amd64

2019-09-30 Thread John Covici 
On Mon, 30 Sep 2019 16:47:29 -0400,
deloptes wrote:
> 
> John Covici wrote:
> 
> > Google did not give me that at all.  I am not trying to build a Debian
> > package,just trying to compile the kernel.
> 
> Then just do
> 
> make deb-pkg
> 
> You could read more about the make system used by the kernel
> 
> https://www.kernel.org/doc/html/latest/
> 
> or in the directory
> 
> $ less README 
> 
> so according Documentation/kbuild/kbuild.txt
> 
> KBUILD_DEBARCH
> --
> For the deb-pkg target, allows overriding the normal heuristics deployed by
> deb-pkg. Normally deb-pkg attempts to guess the right architecture based on
> the UTS_MACHINE variable, and on some architectures also the kernel config.
> The value of KBUILD_DEBARCH is assumed (not checked) to be a valid Debian
> architecture.

I am trying to do something very simple, with the config file supplied
from Debian, I need to do a make bzImage and possible a make modules,
how can dI do this?  Do I need to change the config in some way in
order to do this?

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com

Re: strange error compiling kernel 4.19.0-6-amd64

2019-09-30 Thread deloptes 
John Covici wrote:

> I am doing a straight makebzImage not trying to build a deb package.
> In Debian 9, I could do this with no problem.

Obviously you are trying to build the kernel from debian source. You have to
use the original source, without the debian directory. IF there is debian
directory, it means you decided to use the Debian way.

I do not know how this code is set up, but if you download the kernel from
kernel.org, you should not be getting this message. Otherwise the link I
posted before gives a solution to the problem 

-quote-
Using your current Debian kernel configuration as a starting point

Alternatively, you can use the configuration from a Debian-built kernel that
you already have installed by copying the /boot/config-* file to .config
and then running make oldconfig to only answer new questions.

If you do this, ensure that you modify the configuration to set:

CONFIG_SYSTEM_TRUSTED_KEYS = ""
-quote-

Re: strange error compiling kernel 4.19.0-6-amd64

2019-09-30 Thread deloptes 
John Covici wrote:

> Google did not give me that at all.  I am not trying to build a Debian
> package,just trying to compile the kernel.

Then just do

make deb-pkg

You could read more about the make system used by the kernel

https://www.kernel.org/doc/html/latest/

or in the directory

$ less README 

so according Documentation/kbuild/kbuild.txt

KBUILD_DEBARCH
--
For the deb-pkg target, allows overriding the normal heuristics deployed by
deb-pkg. Normally deb-pkg attempts to guess the right architecture based on
the UTS_MACHINE variable, and on some architectures also the kernel config.
The value of KBUILD_DEBARCH is assumed (not checked) to be a valid Debian
architecture.

Re: strange error compiling kernel 4.19.0-6-amd64

2019-09-30 Thread Reco 
On Mon, Sep 30, 2019 at 04:20:53PM -0400, John Covici wrote:
> > On Mon, Sep 30, 2019 at 04:10:27PM -0400, John Covici wrote:
> > > So, how do I turn this off so I can compile the thing?
> > 
> > "dpkg-buildpackage -b" considers it a warning and skips it.
> > At least it does so for me.
> 
> I am doing a straight makebzImage not trying to build a deb package.
> In Debian 9, I could do this with no problem.

Two choices here:

1) Do it Debian way, which works. Different version, different rules,
and all that.

2) Persisting in your current way, which does not.

I leave a final choice to you.

Reco

Re: strange error compiling kernel 4.19.0-6-amd64

2019-09-30 Thread John Covici 


On Mon, 30 Sep 2019 16:05:16 -0400,
deloptes wrote:
> 
> John Covici wrote:
> 
> > debian/certs/debian-uefi-certs.pem
> 
> https://wiki.debian.org/BuildADebianKernelPackage
> 
> I hope you can read - also find a good search engine - first hit
> 
> 

Google did not give me that at all.  I am not trying to build a Debian
package,just trying to compile the kernel.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com

Re: strange error compiling kernel 4.19.0-6-amd64

2019-09-30 Thread John Covici 
On Mon, 30 Sep 2019 16:15:38 -0400,
Reco wrote:
> 
> Please do not top post.
> 
> On Mon, Sep 30, 2019 at 04:10:27PM -0400, John Covici wrote:
> > So, how do I turn this off so I can compile the thing?
> 
> "dpkg-buildpackage -b" considers it a warning and skips it.
> At least it does so for me.

I am doing a straight makebzImage not trying to build a deb package.
In Debian 9, I could do this with no problem.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com

Re: strange error compiling kernel 4.19.0-6-amd64

2019-09-30 Thread Reco 
Please do not top post.

On Mon, Sep 30, 2019 at 04:10:27PM -0400, John Covici wrote:
> So, how do I turn this off so I can compile the thing?

"dpkg-buildpackage -b" considers it a warning and skips it.
At least it does so for me.

Reco

Re: strange error compiling kernel 4.19.0-6-amd64

2019-09-30 Thread John Covici 
So, how do I turn this off so I can compile the thing?

On Mon, 30 Sep 2019 16:02:02 -0400,
Reco wrote:
> 
>   Hi.
> 
> On Mon, Sep 30, 2019 at 03:46:41PM -0400, John Covici wrote:
> > Hi.  I am getting an error while compiling the kernel 4.19-0-6-amd64.
> > 
> >   CC  kernel/rseq.o
> > AR  kernel/built-in.a
> > make[1]: *** No rule to make target
> > 'debian/certs/debian-uefi-certs.pem', needed by
> > 'certs/x509_certificate_list'.  Stop.
> > 
> > What package do I need to fix this problem?
> 
> It fails at signing your kernel by Debian CA key. They don't provide it
> by any package as it would beat the primary purpose of Restricted Boot
> (Secure Boot in M$ speak).
> 
> 
> > Thanks in advance for any suggestions.
> 
> Follow [1].
> 
> Reco
> 
> [1] 
> https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-common-official
> 

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com

Re: strange error compiling kernel 4.19.0-6-amd64

2019-09-30 Thread deloptes 
John Covici wrote:

> debian/certs/debian-uefi-certs.pem

https://wiki.debian.org/BuildADebianKernelPackage

I hope you can read - also find a good search engine - first hit

Re: strange error compiling kernel 4.19.0-6-amd64

2019-09-30 Thread Sven Joachim 
On 2019-09-30 15:46 -0400, John Covici wrote:

> Hi.  I am getting an error while compiling the kernel 4.19-0-6-amd64.
>
>   CC  kernel/rseq.o
> AR  kernel/built-in.a
> make[1]: *** No rule to make target
> 'debian/certs/debian-uefi-certs.pem', needed by
> 'certs/x509_certificate_list'.  Stop.
>
> What package do I need to fix this problem?

The linux-config-4.19 package[1], it "contains the configuration files
used to build the official Debian kernel files, but without references
to Debian's signing certificates."

HTH,
Sven


1. https://packages.debian.org/buster/linux-config-4.19

Re: strange error compiling kernel 4.19.0-6-amd64

2019-09-30 Thread Reco 
Hi.

On Mon, Sep 30, 2019 at 03:46:41PM -0400, John Covici wrote:
> Hi.  I am getting an error while compiling the kernel 4.19-0-6-amd64.
> 
>   CC  kernel/rseq.o
> AR  kernel/built-in.a
> make[1]: *** No rule to make target
> 'debian/certs/debian-uefi-certs.pem', needed by
> 'certs/x509_certificate_list'.  Stop.
> 
> What package do I need to fix this problem?

It fails at signing your kernel by Debian CA key. They don't provide it
by any package as it would beat the primary purpose of Restricted Boot
(Secure Boot in M$ speak).


> Thanks in advance for any suggestions.

Follow [1].

Reco

[1] 
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-common-official

strange error compiling kernel 4.19.0-6-amd64

2019-09-30 Thread John Covici 
Hi.  I am getting an error while compiling the kernel 4.19-0-6-amd64.

  CC  kernel/rseq.o
AR  kernel/built-in.a
make[1]: *** No rule to make target
'debian/certs/debian-uefi-certs.pem', needed by
'certs/x509_certificate_list'.  Stop.

What package do I need to fix this problem?

Thanks in advance for any suggestions.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com

Re: error compiling kernel: undefined reference to `local symbols

2002-09-23 Thread Osamu Aoki 

Few things,

1. Install gawk and select it over mawk (update-alternatives)
2. If you are using old binutils etc., upgrade them to woody
3. Get new bug free source package (2.4.19)

Osamu

On Mon, Sep 23, 2002 at 03:47:57PM +, Marcio Roberto Teixeira wrote:
> Hi.
> 
> I was compiling the kernel (Debian way) and:
> 
> (root)$ make-kpkg kernel_image
> 
> 
> 
> make[3]: Leaving directory `/usr/src/kernel-source-2.4.16/arch/i386/lib'
> make[2]: Leaving directory `/usr/src/kernel-source-2.4.16/arch/i386/lib'
> ld -m elf_i386 -T

-- 
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +
Osamu Aoki @ Cupertino CA USA, GPG-key: A8061F32
 .''`.  Debian Reference: post-installation user's guide for non-developers
 : :' : http://www.debian.org/doc/manuals/reference/ also http://qref.sf.net
 `. `'  "Our Priorities are Our Users and Free Software" --- Social Contract


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: error compiling kernel: undefined reference to `local symbols

2002-09-23 Thread Stephen Gran 

This one time, at band camp, Marcio Roberto Teixeira said:
> 
> 
> Hi.
> 
> I was compiling the kernel (Debian way) and:
> 
> (root)$ make-kpkg kernel_image
> 
> 
> 
> make[3]: Leaving directory `/usr/src/kernel-source-2.4.16/arch/i386/lib'
> make[2]: Leaving directory `/usr/src/kernel-source-2.4.16/arch/i386/lib'
> ld -m elf_i386 -T
> /usr/src/kernel-source-2.4.16/arch/i386/vmlinux.lds -e stext
> arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o
> init/version.o \--start-group \
> arch/i386/kernel/kernel.o arch/i386/mm/mm.o
>   kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \
>drivers/char/char.o drivers/block/block.o
>drivers/misc/misc.o drivers/net/net.o
>drivers/media/media.o drivers/ide/idedriver.o
>drivers/cdrom/driver.o drivers/pci/driver.o
>drivers/pnp/pnp.o drivers/video/video.o \
>net/network.o \
>/usr/src/kernel-source-2.4.16/arch/i386/lib/lib.a
>/usr/src/kernel-source-2.4.16/lib/lib.a
>/usr/src/kernel-source-2.4.16/arch/i386/lib/lib.a
>\
>--end-group \
>-o vmlinux
> 
> drivers/char/char.o(.data+0x46b4): undefined reference to `local symbols in 
>discarded section .text.exit'
> make[1]: ** [vmlinux] Erro 1
> make[1]: Leaving directory `/usr/src/kernel-source-2.4.16'
> make: ** [stamp-build] Erro 2
> funes:/usr/src/kernel-source-2.4.16#
> 
> What's happening? What means "undefined reference to `local symbols in 
> discarded section .text.exit' "? How can I workaround it?
> 
> My setup: unstable, i386.
> 
> Regards,
> -- 
> Marcio Roberto Teixeira

It's a binutils issue, IIRC.  Debconf even emailed me about it a while
back, but I can't find it right now.  Let's see . . . try the thread
starting here:

http://lists.debian.org/debian-devel/2001/debian-devel-200112/msg00199.html

I think the easy answer is: for this version of binutils, only compile
2.4.17 or newer kernels.

HTH,
Steve
-- 
For the first time we have a weapon that nobody has used for thirty years.
This gives me great hope for the human race.
-- Harlan Ellison



msg03254/pgp0.pgp
Description: PGP signature

error compiling kernel: undefined reference to `local symbols

2002-09-23 Thread Marcio Roberto Teixeira 



Hi.

I was compiling the kernel (Debian way) and:

(root)$ make-kpkg kernel_image



make[3]: Leaving directory `/usr/src/kernel-source-2.4.16/arch/i386/lib'
make[2]: Leaving directory `/usr/src/kernel-source-2.4.16/arch/i386/lib'
ld -m elf_i386 -T
/usr/src/kernel-source-2.4.16/arch/i386/vmlinux.lds -e stext
arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o
init/version.o \--start-group \
arch/i386/kernel/kernel.o arch/i386/mm/mm.o
kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \
 drivers/char/char.o drivers/block/block.o
 drivers/misc/misc.o drivers/net/net.o
 drivers/media/media.o drivers/ide/idedriver.o
 drivers/cdrom/driver.o drivers/pci/driver.o
 drivers/pnp/pnp.o drivers/video/video.o \
 net/network.o \
 /usr/src/kernel-source-2.4.16/arch/i386/lib/lib.a
 /usr/src/kernel-source-2.4.16/lib/lib.a
 /usr/src/kernel-source-2.4.16/arch/i386/lib/lib.a
 \
 --end-group \
 -o vmlinux

drivers/char/char.o(.data+0x46b4): undefined reference to `local symbols in discarded 
section .text.exit'
make[1]: ** [vmlinux] Erro 1
make[1]: Leaving directory `/usr/src/kernel-source-2.4.16'
make: ** [stamp-build] Erro 2
funes:/usr/src/kernel-source-2.4.16#

What's happening? What means "undefined reference to `local symbols in discarded 
section .text.exit' "? How can I workaround it?

My setup: unstable, i386.

Regards,
-- 
Marcio Roberto Teixeira

endereço eletrônico: [EMAIL PROTECTED]
página pessoal: http://www.marciotex.hpg.ig.com.br
chave pública: http://www.marciotex.hpg.ig.com.br/marciotex.gpg

Usuário "tchê" Debian/GNULinux

Porto Alegre - RS - Brasil

"A vida é como uma boa prova escolar: é curta, com múltiplas escolhas."

O "world" não é o Word. Uso LaTeX: viva o código aberto!


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Error compiling kernel 2.4.13

2001-12-16 Thread Daniel Toffetti 
Hi all !

I'm getting the following error: "dereferencing pointer to incomplete 
type" when compiling kernel 2.4.13. This error appears in many 
functions in the files fs.h and locks.h.

I've configured the kernel for supporting NFS. Before exhaustively 
trying to check in/out each NFSs option and compiling again, I would 
like to know if there is some known issue with the NFSs options.

In case it is important, the processor type is 486 and I'm using 
kernel-package.

Thanks in advance for any help !!

Daniel
-- 
"There is no spoon..." - The Matrix

Re: Error compiling kernel 2.4.6 with kernel-package

2001-07-14 Thread Manoj Srivastava 
>>"Jan" == Jan Tammen <[EMAIL PROTECTED]> writes:

 Jan> Hi,
 Jan> I'm trying to compile kernel version 2.4.6 with the latest
 Jan> 'kernel-package' [7.50]. Here's the program's output:

 Jan> tarawa:/usr/src/linux# make-kpkg kernel_image
 Jan> [compiling fine ... snipped]
 Jan> install: cannot stat `debian/README.Debian': No such file or directory
 Jan> debian/tmp-source/usr/share/doc/kernel-image-2.4.6/README.Debian.1st \
 Jan> No such file or directory
 Jan> make: *** [kernel-image-deb] Error 1

 Jan> Any hints or suggestions?

File a Bug? There is a typo in the rules file, and that should
 be fixed in an upload today. (Since I do not use the official
 kernel-source images, I never have a top level README.Debian; and
 hence my tests failed to catch this)

manoj
-- 
 "Hey!  Who took the cork off my lunch??!" Fields
Manoj Srivastava   <[EMAIL PROTECTED]>  
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Error compiling kernel 2.4.6 with kernel-package

2001-07-13 Thread Jan Tammen 
Hi,
I'm trying to compile kernel version 2.4.6 with the latest
'kernel-package' [7.50]. Here's the program's output:

tarawa:/usr/src/linux# make-kpkg kernel_image
[compiling fine ... snipped]
install: cannot stat `debian/README.Debian': No such file or directory
debian/tmp-source/usr/share/doc/kernel-image-2.4.6/README.Debian.1st \
No such file or directory
make: *** [kernel-image-deb] Error 1

Any hints or suggestions?

tia, Jan.

RE: Error compiling kernel 2.4.2

2001-03-28 Thread Jason P. Holland 
have you upgraded all the necessary packages as listed in
/usr/src/linux-2.4.2/Documentation/Changes??  it looks like binutils is not
up to date.

Jason

>
> you will need to replace all occurences of -oformat in the Makefile in
> /usr/src/linux-2.4.2/arch/i386/boot with --oformat
>
> HTH
> Vinh
> * mauro <[EMAIL PROTECTED]> [010328 11:47]:
> >
> >  I'm not able to compile de kernel, exactly when I do the
> "make bzImage"
> >  command I obtain this error:
> >
> >  o bbootsect.s
> >  as -o bbootsect.o bbootsect.s
> >  bbootsect.s: Assembler messages:
> >  bbootsect.s:253: Warning: indirect lcall without `*'
> >  ld -m elf_i386 -Ttext 0x0 -s -oformat binary bbootsect.o
> -o bbootsect
> >  ld: cannot open binary: No such file or directory
> >  make[1]: *** [bbootsect] Error 1
> >  make[1]: Leaving directory `/usr/src/linux-2.4.2/arch/i386/boot'
> >  make: *** [bzImage] Error 2-o bbootsect.s
> >  as -o bbootsect.o bbootsect.s
> >  bbootsect.s: Assembler messages:
> >  bbootsect.s:253: Warning: indirect lcall without `*'
> >  ld -m elf_i386 -Ttext 0x0 -s -oformat binary bbootsect.o
> -o bbootsect
> >  ld: cannot open binary: No such file or directory
> >  make[1]: *** [bbootsect] Error 1
> >  make[1]: Leaving directory `/usr/src/linux-2.4.2/arch/i386/boot'
> >  make: *** [bzImage] Error 2
> >
> >
> >  I really don't know what can I do!! any idea??
> >
> >  Thanks for your help.
> >  Sincerely
> >
> >  Mauro
> >
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
>

Re: Error compiling kernel 2.4.2

2001-03-28 Thread Vinh Truong 
you will need to replace all occurences of -oformat in the Makefile in
/usr/src/linux-2.4.2/arch/i386/boot with --oformat

HTH
Vinh
* mauro <[EMAIL PROTECTED]> [010328 11:47]:
> 
>  I'm not able to compile de kernel, exactly when I do the "make bzImage"
>  command I obtain this error:
>  
>  o bbootsect.s
>  as -o bbootsect.o bbootsect.s
>  bbootsect.s: Assembler messages:
>  bbootsect.s:253: Warning: indirect lcall without `*'
>  ld -m elf_i386 -Ttext 0x0 -s -oformat binary bbootsect.o -o bbootsect
>  ld: cannot open binary: No such file or directory
>  make[1]: *** [bbootsect] Error 1
>  make[1]: Leaving directory `/usr/src/linux-2.4.2/arch/i386/boot'
>  make: *** [bzImage] Error 2-o bbootsect.s
>  as -o bbootsect.o bbootsect.s
>  bbootsect.s: Assembler messages:
>  bbootsect.s:253: Warning: indirect lcall without `*'
>  ld -m elf_i386 -Ttext 0x0 -s -oformat binary bbootsect.o -o bbootsect
>  ld: cannot open binary: No such file or directory
>  make[1]: *** [bbootsect] Error 1
>  make[1]: Leaving directory `/usr/src/linux-2.4.2/arch/i386/boot'
>  make: *** [bzImage] Error 2
>  
>  
>  I really don't know what can I do!! any idea??
>  
>  Thanks for your help.
>  Sincerely
>  
>  Mauro
>

Error compiling kernel 2.4.2

2001-03-28 Thread mauro 



 I'm not able to compile de kernel, exactly when I do the "make bzImage"
 command I obtain this error:
 
 o bbootsect.s
 as -o bbootsect.o bbootsect.s
 bbootsect.s: Assembler messages:
 bbootsect.s:253: Warning: indirect lcall without `*'
 ld -m elf_i386 -Ttext 0x0 -s -oformat binary bbootsect.o -o bbootsect
 ld: cannot open binary: No such file or directory
 make[1]: *** [bbootsect] Error 1
 make[1]: Leaving directory `/usr/src/linux-2.4.2/arch/i386/boot'
 make: *** [bzImage] Error 2-o bbootsect.s
 as -o bbootsect.o bbootsect.s
 bbootsect.s: Assembler messages:
 bbootsect.s:253: Warning: indirect lcall without `*'
 ld -m elf_i386 -Ttext 0x0 -s -oformat binary bbootsect.o -o bbootsect
 ld: cannot open binary: No such file or directory
 make[1]: *** [bbootsect] Error 1
 make[1]: Leaving directory `/usr/src/linux-2.4.2/arch/i386/boot'
 make: *** [bzImage] Error 2
 
 
 I really don't know what can I do!! any idea??
 
 Thanks for your help.
 Sincerely
 
 Mauro

RE: Error compiling kernel

2000-09-07 Thread Jason Holland 
oops, my bad.  you need the bin86 package.  sorry about that.

jason

> -Original Message-
> From: Jason Holland [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 07, 2000 6:18 AM
> To: Gutierrez Family; debian-user@lists.debian.org
> Subject: RE: Error compiling kernel
>
>
> Hi,
>   You need to install binutils, as you are missing the as86 assembler.
> Also, i would run make bzImage, instead of make zImage, compression on the
> kernel will be better.
>
> Jason
>
> -Original Message-
> From: Gutierrez Family [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 06, 2000 11:46 PM
> To: debian-user@lists.debian.org
> Subject: Error compiling kernel
>
>
> Hi everyone,
>
> I tried to re-compile the kernel (to include generic SCSI support for my
> scanner) and ran into problems.  Here's what I did - as far as I can
> remember (following the instructions in the README file found in
> the kernel
> source directory):
>
> 1) logged in as root
> 1) ran the xconfig program and selected my options
> 2) ran 'make dep' (from within /usr/src/kernel-source-2.2.17/)
> 2) ran 'make zImage' ( also from /usr/src/kernel-source-2.2.17/) and it
> compiled for quite a while until I got the following message:
>
> "nm vmlinux | grep -v '\(compiled\)\|\(\.o$\)\|\( [aU]
> \)\|\(\.\.ng$\)\|\(LASH[RL]DI\)' | sort > System.map
> make[1]: Entering directory `/usr/src/kernel-source-2.2.17/arch/i386/boot'
> as86 -0 -a -o bootsect.o bootsect.s
> make[1]: as86: Command not found
> make[1]: *** [bootsect.o] Error 127
> make[1]: Leaving directory `/usr/src/kernel-source-2.2.17/arch/i386/boot'
> make: *** [zImage] Error 2
> navi:/usr/src/linux#   "
>
> Do you know how I can get the kernel compiled fully?
>
> Thanks in advance.
>
>
> --
> Unsubscribe?  mail -s unsubscribe
> [EMAIL PROTECTED] < /dev/null
>
>

RE: Error compiling kernel

2000-09-07 Thread Jason Holland 
Hi,
  You need to install binutils, as you are missing the as86 assembler.
Also, i would run make bzImage, instead of make zImage, compression on the
kernel will be better.

Jason

-Original Message-
From: Gutierrez Family [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 06, 2000 11:46 PM
To: debian-user@lists.debian.org
Subject: Error compiling kernel


Hi everyone,

I tried to re-compile the kernel (to include generic SCSI support for my
scanner) and ran into problems.  Here's what I did - as far as I can
remember (following the instructions in the README file found in the kernel
source directory):

1) logged in as root
1) ran the xconfig program and selected my options
2) ran 'make dep' (from within /usr/src/kernel-source-2.2.17/)
2) ran 'make zImage' ( also from /usr/src/kernel-source-2.2.17/) and it
compiled for quite a while until I got the following message:

"nm vmlinux | grep -v '\(compiled\)\|\(\.o$\)\|\( [aU]
\)\|\(\.\.ng$\)\|\(LASH[RL]DI\)' | sort > System.map
make[1]: Entering directory `/usr/src/kernel-source-2.2.17/arch/i386/boot'
as86 -0 -a -o bootsect.o bootsect.s
make[1]: as86: Command not found
make[1]: *** [bootsect.o] Error 127
make[1]: Leaving directory `/usr/src/kernel-source-2.2.17/arch/i386/boot'
make: *** [zImage] Error 2
navi:/usr/src/linux#   "

Do you know how I can get the kernel compiled fully?

Thanks in advance.

Re: Error compiling kernel

2000-09-07 Thread mcclosk 

   make[1]: Entering directory =
   `/usr/src/kernel-source-2.2.17/arch/i386/boot'
   as86 -0 -a -o bootsect.o bootsect.s
   make[1]: as86: Command not found
   make[1]: *** [bootsect.o] Error 127
   make[1]: Leaving directory =
   `/usr/src/kernel-source-2.2.17/arch/i386/boot'
   make: *** [zImage] Error 2
   navi:/usr/src/linux#   "

   Do you know how I can get the kernel compiled fully?

You need to install the bin86 package:

   Package: bin86
   Status: install ok installed
   Priority: standard
   Section: devel
   Installed-Size: 150
   Maintainer: Juan Cespedes <[EMAIL PROTECTED]>
   Source: linux86
   Version: 0.14.9-3
   Depends: libc6 (>= 2.1)
   Conflicts: linux86
   Description: 16-bit assembler and loader
This is the as86 and ld86 distribution written by Bruce Evans.
It's a complete 8086 assembler and loader which can make 32-bit
code for the 386+ processors (under Linux it's used only to create
the 16-bit bootsector and setup binaries).

Jim

Re: Error compiling kernel

2000-09-07 Thread Glyn Millington 
On Wed, Sep 06, 2000 at 09:46:06PM -0700, thus spake Gutierrez Family:
> Hi everyone,
> 
> I tried to re-compile the kernel (to include generic SCSI support for my 
> scanner) and ran into problems.  Here's what I did - as far as I can remember 
> (following the instructions in the README file found in the kernel source 
> directory):
> 

Only been on Debian for a week, but here goes - just wanted to
point to some helpful docs etc

In the /usr/share/doc/kernel-package directory there should be
a README file which tells you which packages you need to compile
a kernel in the Debian manner - it's a terrific system.

There are further useful docs in the directory produced when you
untar the source-code - especialy look for a file "modules" which
explains in some detail how to build them in. 

On the debian website, at the end of the Installation
Instructions for Intel x86 there is a good short guide to
kernel-compiling - I found it a great help.

HTH

Glyn M.

-- 
   **
   * "The soul is greater than the hum of its parts. "  *
   * Douglas Hoftstatder*
   **

RE: Error compiling kernel

2000-09-07 Thread CHEONG, Shu Yang \[Patrick\] 
I am replying to the list...having read ktb [EMAIL PROTECTED] 's postjust
a question...is the as86 file located in the /, /bin, /sbin , /lib
directories..if so then it explains a possible / corruption before I
attempted to compile the 2.2.17 kernel

Patrick Cheong
Information Systems Assurance
Measat Broadcast Network Systems
e-mail: mailto:[EMAIL PROTECTED]
Visit us at: http://www.astro.com.my

> -Original Message-
> From: CHEONG, Shu Yang [Patrick] [SMTP:[EMAIL PROTECTED]
> Sent: Thursday, September 07, 2000 1:36 PM
> To:   'Gutierrez Family'
> Cc:   debian-user@lists.debian.org
> Subject:  RE: Error compiling kernel
> 
> Hi Gutierrez Family...(and List),
> 
> Hey...I got the same error messsage too while attempting to compile the
> "patched" 2.2.17 kernelI downloaded the patches for 2.2.16 and 2.2.17
> and applied those to my 2.2.15 source tree in /usr/src/linux (->
> /usr/src/2.2.15). I did get some error message while applying the patch
> something about reverse patch...however, I continued pressing enter until
> the end and did a make xconfig, make dep, make modules, make
> bzImageand
> at the last step I got that error message.I have not make
> modules_install yet.any ideas anyone.
> 
> 
> Also, I trashed my / when I enabled dma via hdparm..and I have no idea how
> to recoverI ran fsck and e2fsck over the / partition and numerous
> error
> messages flashed by and the last error message said something about some
> inode gone haywire try using inode 8139 or something...which I did and
> when
> I booted into the woody boxmy root (which housed /lib; /bin; /sbin;
> /tmp; etc) had numerous files/libraries missingCan this be 'rescued'?
> If
> not, I'd have to wait for the Debian 2.2 cdroms to arrive from the States
> via Linux System Labs...
> 
> Patrick Cheong
> Information Systems Assurance
> Measat Broadcast Network Systems
> e-mail: mailto:[EMAIL PROTECTED]
> Visit us at: http://www.astro.com.my
> 
> > -Original Message-
> > From:   Gutierrez Family [SMTP:[EMAIL PROTECTED]
> > Sent:   Thursday, September 07, 2000 12:46 PM
> > To: debian-user@lists.debian.org
> > Subject:Error compiling kernel
> > 
> > Hi everyone,
> >  
> > I tried to re-compile the kernel (to include generic SCSI support for my
> > scanner) and ran into problems.  Here's what I did - as far as I can
> > remember (following the instructions in the README file found in the
> > kernel source directory):
> >  
> > 1) logged in as root
> > 1) ran the xconfig program and selected my options
> > 2) ran 'make dep' (from within /usr/src/kernel-source-2.2.17/)
> > 2) ran 'make zImage' ( also from /usr/src/kernel-source-2.2.17/) and it
> > compiled for quite a while until I got the following message:
> >  
> > "nm vmlinux | grep -v '\(compiled\)\|\(\.o$\)\|\( [aU]
> > \)\|\(\.\.ng$\)\|\(LASH[RL]DI\)' | sort > System.map
> > make[1]: Entering directory
> `/usr/src/kernel-source-2.2.17/arch/i386/boot'
> > as86 -0 -a -o bootsect.o bootsect.s
> > make[1]: as86: Command not found
> > make[1]: *** [bootsect.o] Error 127
> > make[1]: Leaving directory
> `/usr/src/kernel-source-2.2.17/arch/i386/boot'
> > make: *** [zImage] Error 2
> > navi:/usr/src/linux#   "
> >  
> > Do you know how I can get the kernel compiled fully?
> >  
> > Thanks in advance.
> 
> 
> -- 
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] <
> /dev/null

RE: Error compiling kernel

2000-09-07 Thread CHEONG, Shu Yang \[Patrick\] 
Hi Gutierrez Family...(and List),

Hey...I got the same error messsage too while attempting to compile the
"patched" 2.2.17 kernelI downloaded the patches for 2.2.16 and 2.2.17
and applied those to my 2.2.15 source tree in /usr/src/linux (->
/usr/src/2.2.15). I did get some error message while applying the patch
something about reverse patch...however, I continued pressing enter until
the end and did a make xconfig, make dep, make modules, make bzImageand
at the last step I got that error message.I have not make
modules_install yet.any ideas anyone.


Also, I trashed my / when I enabled dma via hdparm..and I have no idea how
to recoverI ran fsck and e2fsck over the / partition and numerous error
messages flashed by and the last error message said something about some
inode gone haywire try using inode 8139 or something...which I did and when
I booted into the woody boxmy root (which housed /lib; /bin; /sbin;
/tmp; etc) had numerous files/libraries missingCan this be 'rescued'? If
not, I'd have to wait for the Debian 2.2 cdroms to arrive from the States
via Linux System Labs...

Patrick Cheong
Information Systems Assurance
Measat Broadcast Network Systems
e-mail: mailto:[EMAIL PROTECTED]
Visit us at: http://www.astro.com.my

> -Original Message-
> From: Gutierrez Family [SMTP:[EMAIL PROTECTED]
> Sent: Thursday, September 07, 2000 12:46 PM
> To:   debian-user@lists.debian.org
> Subject:  Error compiling kernel
> 
> Hi everyone,
>  
> I tried to re-compile the kernel (to include generic SCSI support for my
> scanner) and ran into problems.  Here's what I did - as far as I can
> remember (following the instructions in the README file found in the
> kernel source directory):
>  
> 1) logged in as root
> 1) ran the xconfig program and selected my options
> 2) ran 'make dep' (from within /usr/src/kernel-source-2.2.17/)
> 2) ran 'make zImage' ( also from /usr/src/kernel-source-2.2.17/) and it
> compiled for quite a while until I got the following message:
>  
> "nm vmlinux | grep -v '\(compiled\)\|\(\.o$\)\|\( [aU]
> \)\|\(\.\.ng$\)\|\(LASH[RL]DI\)' | sort > System.map
> make[1]: Entering directory `/usr/src/kernel-source-2.2.17/arch/i386/boot'
> as86 -0 -a -o bootsect.o bootsect.s
> make[1]: as86: Command not found
> make[1]: *** [bootsect.o] Error 127
> make[1]: Leaving directory `/usr/src/kernel-source-2.2.17/arch/i386/boot'
> make: *** [zImage] Error 2
> navi:/usr/src/linux#   "
>  
> Do you know how I can get the kernel compiled fully?
>  
> Thanks in advance.

Re: Error compiling kernel

2000-09-07 Thread ktb 
On Wed, 06 Sep 2000, Eric G . Miller wrote:
> apt-get install bin86 kernel-package
> 
> # cd 
> # make [config | menuconfig | xconfig]
> # make-kpkg clean
> # make-kpkg --revision=[epoch:] kernel_image
> # dpkg -i ../kernel-image*.deb
> 
> See man make-kpkg (really is easier, and dpkg will know about your
> kernel).
> 
> On Wed, Sep 06, 2000 at 09:46:06PM -0700, Gutierrez Family wrote:
> > Hi everyone,
> > 
> > I tried to re-compile the kernel (to include generic SCSI support for
> > my scanner) and ran into problems.  Here's what I did - as far as I
> > can remember (following the instructions in the README file found in
> > the kernel source directory):
> > 
> > 1) logged in as root 1) ran the xconfig program and selected my
> > options 2) ran 'make dep' (from within /usr/src/kernel-source-2.2.17/)
> > 2) ran 'make zImage' ( also from /usr/src/kernel-source-2.2.17/) and
> > it compiled for quite a while until I got the following message:
> > 
> > "nm vmlinux | grep -v '\(compiled\)\|\(\.o$\)\|\( [aU]
> > \)\|\(\.\.ng$\)\|\(LASH[RL]DI\)' | sort > System.map make[1]: Entering
> > directory `/usr/src/kernel-source-2.2.17/arch/i386/boot' as86 -0 -a -o
> > bootsect.o bootsect.s make[1]: as86: Command not found make[1]: ***
  
  This   is why the compile
died.  Install the "bin86" package and try again.  
hth,
kent

Re: Error compiling kernel

2000-09-06 Thread Eric G . Miller 
apt-get install bin86 kernel-package

# cd 
# make [config | menuconfig | xconfig]
# make-kpkg clean
# make-kpkg --revision=[epoch:] kernel_image
# dpkg -i ../kernel-image*.deb

See man make-kpkg (really is easier, and dpkg will know about your
kernel).

On Wed, Sep 06, 2000 at 09:46:06PM -0700, Gutierrez Family wrote:
> Hi everyone,
> 
> I tried to re-compile the kernel (to include generic SCSI support for
> my scanner) and ran into problems.  Here's what I did - as far as I
> can remember (following the instructions in the README file found in
> the kernel source directory):
> 
> 1) logged in as root 1) ran the xconfig program and selected my
> options 2) ran 'make dep' (from within /usr/src/kernel-source-2.2.17/)
> 2) ran 'make zImage' ( also from /usr/src/kernel-source-2.2.17/) and
> it compiled for quite a while until I got the following message:
> 
> "nm vmlinux | grep -v '\(compiled\)\|\(\.o$\)\|\( [aU]
> \)\|\(\.\.ng$\)\|\(LASH[RL]DI\)' | sort > System.map make[1]: Entering
> directory `/usr/src/kernel-source-2.2.17/arch/i386/boot' as86 -0 -a -o
> bootsect.o bootsect.s make[1]: as86: Command not found make[1]: ***
> [bootsect.o] Error 127 make[1]: Leaving directory
> `/usr/src/kernel-source-2.2.17/arch/i386/boot' make: *** [zImage]
> Error 2 navi:/usr/src/linux#   "
> 
> Do you know how I can get the kernel compiled fully?
> 
> Thanks in advance.

-- 
/bin/sh ~/.signature:
Command not found

Error compiling kernel

2000-09-06 Thread Gutierrez Family 




Hi everyone,
 
I tried to re-compile the kernel (to include 
generic SCSI support for my scanner) and ran into problems.  Here's what I 
did - as far as I can remember (following the instructions in the README file 
found in the kernel source directory):
 
1) logged in as root
1) ran the xconfig program and selected my 
options
2) ran 'make dep' (from within 
/usr/src/kernel-source-2.2.17/)
2) ran 'make zImage' ( also from 
/usr/src/kernel-source-2.2.17/) and it compiled for quite a while until I got 
the following message:
 
"nm vmlinux | grep -v 
'\(compiled\)\|\(\.o$\)\|\( [aU] \)\|\(\.\.ng$\)\|\(LASH[RL]DI\)' | sort > 
System.mapmake[1]: Entering directory 
`/usr/src/kernel-source-2.2.17/arch/i386/boot'as86 -0 -a -o bootsect.o 
bootsect.smake[1]: as86: Command not foundmake[1]: *** [bootsect.o] 
Error 127make[1]: Leaving directory 
`/usr/src/kernel-source-2.2.17/arch/i386/boot'make: *** [zImage] Error 
2navi:/usr/src/linux#   "
 
Do you know how I can get the kernel compiled 
fully?
 
Thanks in advance.

Error compiling Kernel

1998-08-17 Thread Hank Fay 
Hi all,

I was recompiling the Kernel for the current stable Hamm (d/l'd from the
FTP site this weekend, along with the rest of my system), just setting some
IP flags etc. for IPMasq, and got the following error:

*** output of make zImage 2>errormsg

In file included from
/usr/src/kernel-source-2.0.34/include/linux/ext2_fs_sb.h:19,
   from /usr/src/kernel-source-2.0.34/include/linux/fs.h:427,
   from /usr/src/kernel-source-2.0.34/include/linux/tty.h:19,
   from /usr/src/kernel-source-2.0.34/include/linux/sched.h:26,
   from /usr/src/kernel-source-2.0.34/include/linux/mm.h:4,
   from ip_sockglue.c:20:
/usr/src/kernel-source-2.0.34/include/linux/ext2_fs.h:325: warning: no
semicolon at end of struct or union
/usr/src/kernel-source-2.0.34/include/linux/ext2_fs.h:325: parse error
before `/'
/usr/src/kernel-source-2.0.34/include/linux/ext2_fs.h:369: parse error
before `}'
make[3]: *** [ip_sockglue.o] Error 1
make[2]: *** [first_rule] Error 2
make[1]: *** [sub_dirs] Error 2
make: *** [linuxsubdirs] Error 2

*** eof

I looked at line 325, which is the third line of the struct for superblocks,
and that looks like a semi-colon to me.  Any thoughts on the matter
appreciated.

Thanks,

Hank Fay