From: Adrian Bunk <bunk@fs.tum.de>
To: James Lamanna <james.lamanna@appliedminds.com>
Cc: "'Linus Torvalds'" <torvalds@transmeta.com>,
shaggy@austin.ibm.com, jfs-discussion@oss.software.ibm.com,
"'Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.60: JFS no longer compiles with gcc 2.95
Date: Tue, 11 Feb 2003 08:27:41 +0100 [thread overview]
Message-ID: <20030211072741.GF17128@fs.tum.de> (raw)
In-Reply-To: <022f01c2d14d$71b46550$39140b0a@amthinking.net>
On Mon, Feb 10, 2003 at 01:43:26PM -0800, James Lamanna wrote:
> >>> This broke the compilation with gcc 2.95:
> <-- snip -->
> ...
> gcc -Wp,-MD,fs/jfs/.super.o.d -D__KERNEL__ -Iinclude -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> -pipe -mpreferred-stack-boundary=2 -march=k6
> -Iinclude/asm-i386/mach-default -nostdinc -iwithprefix include
> -D_JFS_4K -DKBUILD_BASENAME=super -DKBUILD_MODNAME=jfs -c -o
> fs/jfs/super.o fs/jfs/super.c
> fs/jfs/super.c: In function `jfs_fill_super':
> fs/jfs/super.c:335: parse error before `)'
> make[2]: *** [fs/jfs/super.o] Error 1
> <-- snip -->
>
> Curious as to what gcc 2.95 version you are using.
> Seems to compile fine with:
> gcc 2.95.4 20011002
I'm using the same gcc. I should have said that I'm compiling with
CONFIG_JFS_DEBUG. Without CONFIG_JFS_DEBUG it indeed compiles fine.
> --James
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-02-11 7:18 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 19:08 Linux 2.5.60 Linus Torvalds
2003-02-10 20:41 ` Maciej Soltysiak
2003-02-10 21:06 ` Linux 2.5.60 Compile error James Lamanna
2003-02-10 21:38 ` Kevin Corry
2003-02-10 22:50 ` Muli Ben-Yehuda
2003-02-10 21:52 ` Dave Jones
2003-02-11 0:12 ` Another " Vlad@geekizoid.com
2003-02-11 5:21 ` Anthony J. Breeds-Taurima
2003-02-10 21:11 ` Linux 2.5.60 Stephen Hemminger
2003-02-10 21:25 ` James Lamanna
2003-02-10 22:54 ` Linus Torvalds
2003-02-10 20:46 ` 2.5.60: JFS no longer compiles with gcc 2.95 Adrian Bunk
2003-02-10 21:43 ` James Lamanna
2003-02-11 7:27 ` Adrian Bunk [this message]
2003-02-12 14:52 ` [PATCH - 2.5.60] " Dave Kleikamp
2003-02-12 15:04 ` Adrian Bunk
2003-02-12 15:42 ` Dave Kleikamp
2003-02-12 16:22 ` Andreas Schwab
2003-02-10 22:21 ` Linux 2.5.60 John Cherry
2003-02-11 7:08 ` Oleg Drokin
2003-02-11 7:38 ` Linus Torvalds
2003-02-12 8:11 ` Eric W. Biederman
2003-02-12 11:49 ` Jeff Dike
2003-02-13 23:25 ` Werner Almesberger
2003-02-11 15:16 ` Zephaniah E. Hull
2003-02-11 22:47 ` Andrew Morton
2003-02-11 22:54 ` Andrew Morton
2003-02-14 16:56 ` Zephaniah E. Hull
2003-02-11 16:23 ` Russell King
2003-02-11 17:06 ` Linus Torvalds
2003-02-12 2:47 ` David S. Miller
2003-02-11 16:44 ` 2.5.60: arlan.c no longer compiles Adrian Bunk
2003-02-11 23:08 ` Andrew Morton
2003-02-11 18:16 ` 2.5.60: sim710.c doesn't compile Adrian Bunk
2003-02-11 18:21 ` James Bottomley
2003-02-11 22:00 ` Linux 2.5.60 Rudmer van Dijk
2003-02-12 10:05 ` Ingo Oeser
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=20030211072741.GF17128@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=james.lamanna@appliedminds.com \
--cc=jfs-discussion@oss.software.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@austin.ibm.com \
--cc=torvalds@transmeta.com \
/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