public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Thomas Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: A compiling procedure question.
Date: Sun, 13 Jan 2002 02:14:14 -0500	[thread overview]
Message-ID: <004001c19c01$e8eb0020$0100a8c0@tward> (raw)
In-Reply-To: <Pine.LNX.4.44.0201122101430.213-100000@rocky.nycap.rr.com>

Hi, I would use make menuconfig. That way you can change sections that you
want without having to answer every bloody question in the make config.

----- Original Message -----
From: Dan Murphy <mweeby@nycap.rr.com>
To: Speakup mailing list <speakup@braille.uwo.ca>
Sent: Saturday, January 12, 2002 9:17 PM
Subject: A compiling procedure question.


> Hi again folks.
> Although I have read the howto on compiling kernels, and I have done
> it successfully before, I don't understand some of the science behind
> some of the procedures, so here's my question.
> I compiled the 2.4.5 kernel, but during make config, I got distracted,
> and in the sound section I pressed n instead of y.
> I didn't realize this UN till later.  Is there a way I can go back in
> and do it again without blowing away my whole source tree and starting
> fresh?  If not, I don't mind, but I am hoping there's an easier way.
> Some of the information in the kernel howto was a bit over my head.
> thanks.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



      parent reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Dan Murphy
 ` Janina Sajka
   ` Steve Holmes
 ` Terry Cudney
 ` Gregory Nowak
   ` Raul A. Gallegos
     ` Gregory Nowak
     ` Geoff Shang
 ` Thomas Ward [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='004001c19c01$e8eb0020$0100a8c0@tward' \
    --to=tward@bright.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).