From: Christian Kujau <evil@g-house.de>
To: linuxppc-dev@lists.linuxppc.org
Subject: linux-2.4-benh compiling error
Date: Tue, 27 Jan 2004 15:30:38 +0100 [thread overview]
Message-ID: <4016760E.50009@g-house.de> (raw)
hi,
i was about to compile linux-2.4-benh (fresh tree fetched via rsync)
when errors occured:
[...]
make[3]: Entering directory
`/data/MP3/scratch/kernel/linux-2.4-benh/drivers/char'
gcc -D__KERNEL__ -I/data/MP3/scratch/kernel/linux-2.4-benh/include -Wall
- -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
- -fomit-frame-pointer -I/data/MP3/scratch/kernel/linux-2.4-benh/arch/ppc
- -fsigned-char -msoft-float -pipe -ffixed-r2 -Wno-uninitialized
- -mmultiple -mstring -nostdinc -iwithprefix include
- -DKBUILD_BASENAME=defkeymap -c -o defkeymap.o defkeymap.c
defkeymap.c:1: error: parse error before "defkeymap"
In file included from
/data/MP3/scratch/kernel/linux-2.4-benh/include/linux/types.h:15,
~ from defkeymap.c:6:
/data/MP3/scratch/kernel/linux-2.4-benh/include/linux/posix_types.h:38:
warning: type defaults to `int' in declaration of `__kernel_fd_set'
/data/MP3/scratch/kernel/linux-2.4-benh/include/linux/posix_types.h:38:
warning: data definition has no type or storage class
line-wrapping sucks, heres the full log and more info:
http://nerdbynature.de/bits/sheep/2.4.24-benh/make.log
http://nerdbynature.de/bits/sheep/2.4.24-benh/config
http://nerdbynature.de/bits/sheep/2.4.24-benh/ver_linux
i was told the 2.4-benh tree could fix some PReP annoyances (sp?) too,
so i wanted to try it out.
Thank you for your time,
Christian.
- --
BOFH excuse #259:
Someone's tie is caught in the printer, and if anything else gets
printed, he'll be in it too.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-01-27 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 14:30 Christian Kujau [this message]
2004-01-27 19:40 ` linux-2.4-benh compiling error David Kimdon
2004-01-27 23:51 ` Christian Kujau
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=4016760E.50009@g-house.de \
--to=evil@g-house.de \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).