From: Dieter R Kedrowitsch <dieter.kedrowitsch@gmail.com>
To: linux-8086@vger.kernel.org
Subject: Re: MAKE errors when trying to compile in Ubuntu 9.10
Date: Tue, 2 Mar 2010 19:52:56 +0000 (UTC)
Date: Wed, 03 Mar 2010 14:53:46 -0500 [thread overview]
Message-ID: <4B8EBE4A.8070309@gmail.com> (raw)
In-Reply-To: <4B8CAF58.6060105@spamgourmet.com>
Switching from dash to bash solved that problem, thanks!
However, now I'm running into a different issue when building. It seems
BCC isn't happy with xt_key.c....
Has anyone seen this before?
bcc -0 -O -I/home/dkedrowitsch/elks/include
-DELKS_VERSION_CODE=0x00010201 -DUTS_RELEASE=\"0.1.3-pre1\" -D__KERNEL__
-ansi -c -o xt_key.o xt_key.c
xt_key.c:168.32: error: xtkb_scan_caps undeclared
xt_key.c:168.37: error: illegal indirection
xt_key.c:170.35: error: xtkb_scan_shifted undeclared
xt_key.c:170.40: error: illegal indirection
xt_key.c:175.36: error: xtkb_scan_ctrl_alt undeclared
xt_key.c:175.41: error: illegal indirection
xt_key.c:182.41: error: illegal indirection
xt_key.c:185.27: error: xtkb_scan undeclared
xt_key.c:185.32: error: illegal indirection
xt_key.c:188.40: error: illegal indirection
xt_key.c:190.40: error: illegal indirection
make[2]: *** [xt_key.o] Error 1
make[2]: Leaving directory `/home/dkedrowitsch/elks/arch/i86/drivers/char'
make[1]: *** [drivers/char/chr_drv.a] Error 2
make[1]: Leaving directory `/home/dkedrowitsch/elks/arch/i86'
make: *** [Image] Error 2
next prev parent reply other threads:[~2010-03-02 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1750932Ab0CAFCB/20100301050201Z+473@vger.kernel.org>
2010-03-01 6:24 ` MAKE errors when trying to compile in Ubuntu 9.10 Dieter R Kedrowitsch
2010-03-01 9:31 ` Frank Gevaerts
2010-03-02 19:24 ` Harley Laue
2010-03-02 19:52 ` Dieter R Kedrowitsch [this message]
2010-03-02 20:24 ` Harley Laue
2010-03-02 20:37 ` MAKE errors when trying to compile in Ubuntu 9.10 (nospam: message 9 of 20) Dieter R Kedrowitsch
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=4B8EBE4A.8070309@gmail.com \
--to=dieter.kedrowitsch@gmail.com \
--cc=linux-8086@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.