From: Jesper Juhl <juhl@eisenstein.dk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: MCradiolists: line 2: syntax error near unexpected token
Date: Thu, 10 May 2001 01:55:27 +0200 [thread overview]
Message-ID: <3AF9D8EF.4020605@eisenstein.dk> (raw)
In-Reply-To: <E14xbcH-0003LC-00@the-village.bc.nu>
Alan Cox wrote:
>> I just unpacked a fresh copy of 2.4.4 and patched it to 2.4.5pre1 and
>> ran into a problem. When I attempt to change the type (through
>> menuconfig) of CPU to compile for, the following gets dumped to the
>> console:
>
>
> Grab the menuconfig diff from the -ac patches . Menuconfig had a bug in
> bracket handling the new config file tripped
I extracted the menuconfig related parts from 2.4.4-ac6 and applied them
- with 100% success... I can now select the CPU type.
Thank you!
Best regards,
Jesper Juhl - juhl@eisenstein.dk
prev parent reply other threads:[~2001-05-09 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-09 23:20 MCradiolists: line 2: syntax error near unexpected token Jesper Juhl
2001-05-09 21:35 ` Alan Cox
2001-05-09 23:55 ` Jesper Juhl [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=3AF9D8EF.4020605@eisenstein.dk \
--to=juhl@eisenstein.dk \
--cc=alan@lxorguk.ukuu.org.uk \
--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