All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Weber <weber@nyc.rr.com>
To: linux-kernel@vger.kernel.org
Subject: 2.5.3-pre1 compile error
Date: Tue, 15 Jan 2002 19:05:10 -0500	[thread overview]
Message-ID: <3C44C3B6.8060900@nyc.rr.com> (raw)

gcc -D__KERNEL__ -I/usr/src/linux-2.5.2/include -Wall 
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer 
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 
-march=i686    -c -o read_write.o read_write.c
In file included from read_write.c:10:
/usr/src/linux-2.5.2/include/linux/file.h:25: parse error before `atomic_t'
/usr/src/linux-2.5.2/include/linux/file.h:25: warning: no semicolon at 
end of struct or union
/usr/src/linux-2.5.2/include/linux/file.h:36: parse error before `}'
/usr/src/linux-2.5.2/include/linux/file.h: In function `fcheck_files':
/usr/src/linux-2.5.2/include/linux/file.h:50: dereferencing pointer to 
incomplete type
/usr/src/linux-2.5.2/include/linux/file.h:51: dereferencing pointer to 
incomplete type
In file included from read_write.c:13:
/usr/src/linux-2.5.2/include/linux/dnotify.h: At top level:
/usr/src/linux-2.5.2/include/linux/dnotify.h:18: warning: `struct inode' 
declared inside parameter list
/usr/src/linux-2.5.2/include/linux/dnotify.h:18: warning: its scope is 
only this definition or declaration, which is probably not what you want.
/usr/src/linux-2.5.2/include/linux/dnotify.h:21: warning: `struct inode' 
declared inside parameter list
/usr/src/linux-2.5.2/include/linux/dnotify.h: In function 
`inode_dir_notify':
/usr/src/linux-2.5.2/include/linux/dnotify.h:23: dereferencing pointer 
to incomplete type
/usr/src/linux-2.5.2/include/linux/dnotify.h:24: warning: passing arg 1 
of `__inode_dir_notify' from incompatible pointer type
read_write.c: In function `sys_read':
read_write.c:167: warning: passing arg 1 of `inode_dir_notify' from 
incompatible pointer type
read_write.c: In function `sys_write':
read_write.c:194: warning: passing arg 1 of `inode_dir_notify' from 
incompatible pointer type
read_write.c: In function `do_readv_writev':
read_write.c:299: warning: passing arg 1 of `inode_dir_notify' from 
incompatible pointer type
read_write.c: In function `sys_pread':
read_write.c:371: warning: passing arg 1 of `inode_dir_notify' from 
incompatible pointer type
read_write.c: In function `sys_pwrite':
read_write.c:403: warning: passing arg 1 of `inode_dir_notify' from 
incompatible pointer type
make[2]: *** [read_write.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.5.2/fs'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/src/linux-2.5.2/fs'
make: *** [_dir_fs] Error 2


             reply	other threads:[~2002-01-16  0:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-16  0:05 John Weber [this message]
2002-01-16  0:20 ` [PATCH] Re: 2.5.3-pre1 compile error Benjamin LaHaise
2002-01-16  0:29   ` Linus Torvalds
2002-01-16  0:38     ` David Weinehall
2002-01-16  0:41       ` Linus Torvalds
2002-01-16  0:55         ` Dave Jones
2002-01-16  2:10           ` dmeyer
2002-01-16 18:32           ` Peter Osterlund
2002-01-16  0:43     ` Benjamin LaHaise
2002-01-16  0:44       ` Linus Torvalds
2002-01-16  0:52         ` Benjamin LaHaise
2002-01-16  1:18           ` David Weinehall
2002-01-17 22:11         ` Christopher Turcksin
2002-01-16  1:24       ` Robert Love
2002-01-16  1:25         ` Benjamin LaHaise
2002-01-16  1:39           ` Robert Love
2002-01-16  0:46     ` Davide Libenzi
2002-01-16  0:43       ` Linus Torvalds
2002-01-16  0:52         ` David S. Miller
2002-01-16  1:06           ` Andre Hedrick
2002-01-16  1:17         ` Davide Libenzi
2002-01-16  1:23           ` Davide Libenzi
  -- strict thread matches above, loose matches on Subject: below --
2002-01-16  1:30 Dave Jones
2002-01-16  1:57 ` Alan Cox
2002-01-16  2:43   ` David S. Miller

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=3C44C3B6.8060900@nyc.rr.com \
    --to=weber@nyc.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 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.