mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Max Linux" <max.linux@ntlworld.com>
To: <linux-kernel@vger.kernel.org>
Subject: Kernel compile and speakup
Date: Sat, 19 Apr 2003 21:56:35 +0100	[thread overview]
Message-ID: <006101c306b6$2a52f480$6b7ba8c0@max> (raw)

Hi

As a Linux newbie, I have been trying to compile a new Linux kernel to give
me raid support.

This was easy the first time, but has failed the second time round, for a
reason I cannot understand.

Using the procedure:

bash# make mrproper
bash# make xconfig

< select all the options I want (including raid support) >

bash# make dep
bash# make clean
bash# make bzImage

The make fails, with the following errors:

In file included from console.c:110:
/usr/src/linux-2.4.18-27.7.x/include/linux/speakup.h:186:25: operator '('
has no left operand
make[3]: *** [console.o] Error 1
make[3]: Leaving directory '/usr/src/linux-2.4.18-27.7.x/drivers/char'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory '/usr/src/linux-2.4.18-27.7.x/drivers/char'
make[1]: *** [_subdir_char] Error 2
make[1]: Leaving directory '/usr/src/linux-2.4.18-27.7.x/drivers'
make: *** [_dir_drivers] Error 2

As far as I can see, there is no reason for speakup.h to be included in the
make. However, since it is there, there is no reason for this error to
occur.
NOTE: The left bracket in the quotes is what is reported, although the
character in speakup.h is <.

speakup is specifically not requested in xconfig, as the vga console.

Please tell me what I have done wrong. As I said before, the previous
compilation went fine. Something has since broken.

Thanks in advance.

Max Booker
max.linux@ntlworld.com


                 reply	other threads:[~2003-04-19 20:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='006101c306b6$2a52f480$6b7ba8c0@max' \
    --to=max.linux@ntlworld.com \
    --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

all inboxes | Powered by JetHome®