mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: LKML <linux-kernel@vger.kernel.org>
Subject: 2.5.25 -- Build error -- fs/ntfs/layout.h:299: unnamed fields of type other than struct or union are not allowed
Date: Sun, 07 Jul 2002 23:53:17 -0700	[thread overview]
Message-ID: <3D2936DD.5040700@megapathdsl.net> (raw)

  gcc -Wp,-MD,./.aops.o.d -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=athlon  -nostdinc -iwithprefix include -DMODULE -DNTFS_VERSION=\"2.0.14\" -DDEBUG  -DKBUILD_BASENAME=aops   -c -o aops.o aops.c
In file included from inode.h:29,
                 from debug.h:30,
                 from ntfs.h:40,
                 from aops.c:30:
layout.h:299: unnamed fields of type other than struct or union are not allowed
layout.h:1449: unnamed fields of type other than struct or union are not allowed
layout.h:1465: unnamed fields of type other than struct or union are not allowed
layout.h:1714: unnamed fields of type other than struct or union are not allowed
layout.h:1891: unnamed fields of type other than struct or union are not allowed
layout.h:2051: unnamed fields of type other than struct or union are not allowed
layout.h:2063: unnamed fields of type other than struct or union are not allowed
make[2]: *** [aops.o] Error 1
make[2]: Leaving directory `/usr/src/linux/fs/ntfs'

CONFIG_QUOTA=y
CONFIG_QFMT_V1=m
CONFIG_QFMT_V2=m
CONFIG_QUOTACTL=y
CONFIG_AUTOFS4_FS=y
CONFIG_EXT3_FS=y
CONFIG_FAT_FS=m
CONFIG_VFAT_FS=m
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_NTFS_FS=m
CONFIG_NTFS_DEBUG=y



             reply	other threads:[~2002-07-08  6:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-08  6:53 Miles Lane [this message]
2002-07-08  7:22 ` 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=3D2936DD.5040700@megapathdsl.net \
    --to=miles@megapathdsl.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 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®