From: "Axel H. Siebenwirth" <axel@hh59.org>
To: linux-kernel@vger.kernel.org
Cc: aia21@cantab.net
Subject: [2.5.15] NTFS does not compile. (with gcc3.1)
Date: Wed, 15 May 2002 02:41:13 +0200 [thread overview]
Message-ID: <20020515004113.GA21702@neon> (raw)
Dear kernel developers,
I know, I know, I am not supposed to use gcc 3.x with linux kernel build,
but maybe someone can just give me a hint what gcc option to add to NTFS
build to get it to work?
I just tried to build 2.5.15 and it stops during compilation of
fs/ntfs/aops.c because of included header file layout.h:
gcc -D__KERNEL__ -I/usr/src/linux-2.5.15/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common
-pipe -mpreferred-stack-boundary=2 -march=i686 -DNTFS_VERSION=\"2.0.6\"
-DDEBUG -DKBUILD_BASENAME=aops -c -o aops.o aops.c
In file included from attrib.h:31,
from debug.h:31,
from ntfs.h:43,
from aops.c:30:
layout.h:299: unnamed fields of type other than struct or union are not
allowed
layout.h:1450: unnamed fields of type other than struct or union are not
allowed
layout.h:1466: unnamed fields of type other than struct or union are not
allowed
layout.h:1715: unnamed fields of type other than struct or union are not
allowed
layout.h:1892: unnamed fields of type other than struct or union are not
allowed
layout.h:2052: unnamed fields of type other than struct or union are not
allowed
layout.h:2064: unnamed fields of type other than struct or union are not
allowed
make[3]: *** [aops.o] Error 1
make[3]: Leaving directory /usr/src/linux-2.5.15/fs/ntfs'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory /usr/src/linux-2.5.15/fs/ntfs'
make[1]: *** [_subdir_ntfs] Error 2
make[1]: Leaving directory /usr/src/linux-2.5.15/fs'
make: *** [_dir_fs] Error 2
Regards,
Axel
next reply other threads:[~2002-05-15 0:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 0:41 Axel H. Siebenwirth [this message]
2002-05-15 1:01 ` [2.5.15] NTFS does not compile. (with gcc3.1) Anton Altaparmakov
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=20020515004113.GA21702@neon \
--to=axel@hh59.org \
--cc=aia21@cantab.net \
--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 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.