mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Cole <elenstev@mesatop.com>
To: Anton Kholodenin <cicprogr@mail.dux.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Make Menuconfig and Make Xconfig errors in Mandrake 9.2 rc1
Date: 09 Sep 2003 09:58:03 -0600	[thread overview]
Message-ID: <1063123083.1663.34.camel@spc9.esa.lanl.gov> (raw)
In-Reply-To: <1063115985.1664.14.camel@spc9.esa.lanl.gov>

On Tue, 2003-09-09 at 07:59, Steven Cole wrote:
> On Tue, 2003-09-09 at 04:06, Anton Kholodenin wrote:
> > I find 2 errors in Mandrake 9.2 rc 1
> > 
> As others noted, a Mandrake-specific list is a better choice in this
> instance, but the problem you noted below happens occasionally in 2.4
> bleeding edge stuff, so I'm posting something for you to look for.
> > 
> > 2. If i do cd /usr/src/linux; make xconfig program not started and write to
> > console:
> 
>3rdparty/lufs/Config.in: 2: can't handle
dep_bool/dep_mbool/dep_tristate

Replying to myself, apologies to all for the previous noise.
I hadn't looked at the error closely enough.  My previous post was not
apropos to Anton's specific problem.

Try doing this from /usr/src/linux:
grep dep_ 3rdparty/lufs/Config.in

You'll see various lines with something like:
dep_tristate ' Some prompt' CONFIG_SOMETHING $CONFIG_SOMETHINGELSE

The $CONFIG_SOMETHINGELSE may be missing on some line.  You can kludge
it by changing the dep_tristate to a plain tristate.

The Mandrake 9.2 rc2 is out now, so you might want to look at that
instead.

Steven




      reply	other threads:[~2003-09-09 16:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-09 10:06 Anton Kholodenin
2003-09-09 12:09 ` Stuart Longland
2003-09-09 13:59 ` Steven Cole
2003-09-09 15:58   ` Steven Cole [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=1063123083.1663.34.camel@spc9.esa.lanl.gov \
    --to=elenstev@mesatop.com \
    --cc=cicprogr@mail.dux.ru \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome