public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gnea" <gnea@rochester.rr.com>
To: "LKML" <linux-kernel@vger.kernel.org>
Subject: 240t11p6: NTFS broken (again? :) )
Date: 17 Nov 2000 03:50:42 EST	[thread overview]
Message-ID: <20001117084625.AAA13225@mail2.nyroc.rr.com@celery> (raw)

Compiling as a module, the following throws a tantrum in my face:

make[2]: Entering directory `/usr/src/linux/fs/ntfs'
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe
-mpreferred-stack-boundary=2 -march=i686 -malign-functions=4  -DMODULE
-DNTFS_IN_LINUX_KERNEL -DNTFS_VERSION=\"000607\" -c -o inode.o inode.c
inode.c:1054: conflicting types for `new_inode'
/usr/src/linux/include/linux/fs.h:1153: previous declaration of
`new_inode'
make[2]: *** [inode.o] Error 1
make[2]: Leaving directory `/usr/src/linux/fs/ntfs'

and proceeds to die.. btw, this is for "make modules".. the kernel
built just fine (tho i haven't booted it yet)

i still suck at C, so this is only a guess (i'll find out if i'm right
or wrong i suppose ;) ), is that you can't static int without a
function prototype for it ... or a static inline can't be a static
int... well whatever the case, i look forward to seeing the fix [and
now it's time for sleep now that i am about to faceplant] ;)

-- 
	.oO gnea at rochester dot rr dot com Oo.
	    .oO url: http://garson.org/~gnea Oo.

"You can tune a filesystem, but you can't tuna fish" -unknown

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

                 reply	other threads:[~2000-11-17  9:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20001117084625.AAA13225@mail2.nyroc.rr.com@celery \
    --to=gnea@rochester.rr.com \
    --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