🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.linux
Article #701

Re: Using make menuconfig

#701
From: Rick Runowski
Date: Sun, 28 Mar 1999 00:00
47 lines
2953 bytes
Ok, I ran into a problem seconds after my last post... I was performing
the make boot, and the program exited with:

(last few lines)

nm vmlinux | grep -v '\(compiled\)\|\(\.o$)\|\( [aU]
\_\|\(\.\.ng$\)\|\(LASH[RL]DI\)' | sort > System.map
make [1]: entering directory '/usr/src/linux-2.2.4/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/linux-2.2.4/arch/i386/boot'
make: *** [boot] Error 2

What did I do wrong?

Thanks in advance!

Rick

On Sat, 27 Mar 1999, Christian D Freet wrote:

> The newly compiled kernel is, I believe, in the /usr/src/linux/arch/i386/boot/ directory and
> it's called zImage, if you used the "make zImage" command... if you used the "make bzImage"
> command, as I did, it will be named bzImage.  Check out
> http://www.redhat.com/knowledgebase/kb/cache/37.html
> 
> There is a good description of how to finish... make sure, after you copy the image to where
> ever you want it to stay permanently, that you modify the lilo.conf file to point to it (see
> the file... you'll know what I mean).  Then run lilo (e.g. type "lilo, [enter]") to map the
> kernel... then reboot.
> 
> On Fri, 26 Mar 1999 20:04:05 -0600, Rick Runowski <runowsk@okstate.edu> wrote:
> 
> >
> >Actually I am having a similar problem.  I downloaded the latest kernel
> >from ftp.kernel and I un tar/gz'ed it and I printed the instructions and
> >followed them.. I got to the compile Kernel... where is the kernel at?  Do
> >I use cc kernel... I can't find the instructions on compiling... I'm very
> >new to this... but where do I look... I tried the command below and got
> >about four lines all of which have errors on them?  Any help is
> >appreciated.
> >
> >Thanks
> >
--SNIP--
Technical Details
Message-ID: <Pine.DU4.3.96.990328164935.5788B-100000@osuunx.ucc.okstate.edu>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <36f9ce5a.247951@news.eatel.net> <36fa7335.7375496@news.i1.net> <36fbb341.454664@news.eatel.net> <2742@gos.ukc.ac.uk> <Pine.DU4.3.96.990326200143.15179B-100000@osuunx.ucc.okstate.edu> <36fe571c.3199541@news.eatel.net>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 102b32,3e44b8d909efedf9
X-Google-Attributes: gid102b32,public
X-Google-Thread: faa64,3e44b8d909efedf9
X-Google-Attributes: gidfaa64,public
X-Google-Thread: f9382,3e44b8d909efedf9
X-Google-Attributes: gidf9382,public
X-Google-Thread: 100c5f,3e44b8d909efedf9
X-Google-Attributes: gid100c5f,public
X-Google-Thread: 102983,3e44b8d909efedf9
X-Google-Attributes: gid102983,public
From: Rick Runowski <runowsk@okstate.edu>
Subject: Re: Using make menuconfig
Date: 1999/03/28
Message-ID: <Pine.DU4.3.96.990328164935.5788B-100000@osuunx.ucc.okstate.edu>
X-Deja-AN: 460133477
References: <36f9ce5a.247951@news.eatel.net> <36fa7335.7375496@news.i1.net> <36fbb341.454664@news.eatel.net> <2742@gos.ukc.ac.uk> <Pine.DU4.3.96.990326200143.15179B-100000@osuunx.ucc.okstate.edu> <36fe571c.3199541@news.eatel.net>
X-Sender: runowsk@osuunx.ucc.okstate.edu
Content-Type: TEXT/PLAIN; charset=US-ASCII
Organization: Oklahoma State University
Mime-Version: 1.0
Newsgroups: alt.linux,alt.os.linux,aus.computers.linux,comp.os.linux,comp.os.linux.hardware