From: David Ford <david+cert@blue-labs.org>
To: linux-kernel@vger.kernel.org
Subject: 2.5.2 - reiserfs::procfs.c fails compile
Date: Tue, 15 Jan 2002 14:25:53 -0500 [thread overview]
Message-ID: <3C448241.7000104@blue-labs.org> (raw)
Looks like a quick fix, ..I haven't inspected it tho.
-d
gcc -D__KERNEL__ -I/usr/local/src/linux/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
-march=i686 -DSMBFS_PARANOIA -c -o inode.o inode.c
procfs.c: In function `reiserfs_version_in_proc':
procfs.c:80: conversion to non-scalar type requested
procfs.c: In function `reiserfs_super_in_proc':
procfs.c:137: conversion to non-scalar type requested
procfs.c: In function `reiserfs_per_level_in_proc':
procfs.c:217: conversion to non-scalar type requested
procfs.c: In function `reiserfs_bitmap_in_proc':
procfs.c:296: conversion to non-scalar type requested
procfs.c: In function `reiserfs_on_disk_super_in_proc':
procfs.c:337: conversion to non-scalar type requested
procfs.c: In function `reiserfs_oidmap_in_proc':
procfs.c:390: conversion to non-scalar type requested
procfs.c: In function `reiserfs_journal_in_proc':
procfs.c:441: conversion to non-scalar type requested
procfs.c:494: incompatible type for argument 1 of `bdevname'
procfs.c: In function `reiserfs_proc_register':
procfs.c:581: aggregate value used where an integer was expected
make[3]: *** [procfs.o] Error 1
make[3]: Leaving directory `/usr/local/src/linux/fs/reiserfs'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/local/src/linux/fs/reiserfs'
next reply other threads:[~2002-01-15 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 19:25 David Ford [this message]
2002-01-15 19:40 ` 2.5.2 - reiserfs::procfs.c fails compile Dave Jones
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=3C448241.7000104@blue-labs.org \
--to=david+cert@blue-labs.org \
--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.