From: Rene Engelhard <mail@rene-engelhard.de>
To: linux-kernel@vger.kernel.org
Subject: Compile error 2.5.2-pre8 (ext3)
Date: Sat, 5 Jan 2002 17:57:27 +0100 [thread overview]
Message-ID: <20020105175727.A10286@rene-engelhard.de> (raw)
Hi,
I got the following trying to compile linux-2.5.2-pre8...
make[3]: Entering directory
`/home/rene/Entwicklung/Kernel/linux-2.5.2-pre8/fs/ext3'
gcc -D__KERNEL__
-I/home/rene/Entwicklung/Kernel/linux-2.5.2-pre8/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686 -c -o balloc.o balloc.c
gcc -D__KERNEL__
-I/home/rene/Entwicklung/Kernel/linux-2.5.2-pre8/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686 -c -o bitmap.o bitmap.c
gcc -D__KERNEL__
-I/home/rene/Entwicklung/Kernel/linux-2.5.2-pre8/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686 -c -o dir.o dir.cgcc -D__KERNEL__
-I/home/rene/Entwicklung/Kernel/linux-2.5.2-pre8/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686 -c -o file.o file.c
gcc -D__KERNEL__
-I/home/rene/Entwicklung/Kernel/linux-2.5.2-pre8/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686 -c -o fsync.o fsync.c
gcc -D__KERNEL__
-I/home/rene/Entwicklung/Kernel/linux-2.5.2-pre8/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686 -c -o ialloc.o ialloc.c
gcc -D__KERNEL__
-I/home/rene/Entwicklung/Kernel/linux-2.5.2-pre8/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686 -c -o inode.o inode.c
gcc -D__KERNEL__
-I/home/rene/Entwicklung/Kernel/linux-2.5.2-pre8/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686 -c -o ioctl.o ioctl.c
gcc -D__KERNEL__
-I/home/rene/Entwicklung/Kernel/linux-2.5.2-pre8/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686 -c -o namei.o namei.c
gcc -D__KERNEL__
-I/home/rene/Entwicklung/Kernel/linux-2.5.2-pre8/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686 -c -o super.o super.c
super.c: In function `make_rdonly':
super.c:59: invalid operands to binary !=
super.c:62: invalid operands to binary +
make[3]: *** [super.o] Error 1
make[2]: *** [first_rule] Error 2
make[1]: *** [_subdir_ext3] Error 2
make: *** [_dir_fs] Error 2
make[3]: Leaving directory
`/home/rene/Entwicklung/Kernel/linux-2.5.2-pre8/fs/ext3'
make[2]: Leaving directory
`/home/rene/Entwicklung/Kernel/linux-2.5.2-pre8/fs/ext3'
make[1]: Leaving directory
`/home/rene/Entwicklung/Kernel/linux-2.5.2-pre8/fs'
rene@ReneEngelhard:~/Entwicklung/Kernel/linux-2.5.2-pre8>
Does anyone know what do do here now?
I _have_ to compile the kernel with ext3 because / and all partitions
are ext3...
Rene
--
GnuPG:
Key fingerprint = 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73
Key ID: 248AEB73
Mail an gnupgkey@rene-engelhard.de um den Key zugeschickt zu bekommen
Mail to gnupgkey@rene-engelhard.de to get the key automatically
next reply other threads:[~2002-01-05 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-05 16:57 Rene Engelhard [this message]
2002-01-05 17:14 ` Rene Engelhard
2002-01-08 18:37 ` Roeland Th. Jansen
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=20020105175727.A10286@rene-engelhard.de \
--to=mail@rene-engelhard.de \
--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®