From: Miles Lane <miles@megapathdsl.net>
To: LKML <linux-kernel@vger.kernel.org>
Subject: 2.5.2-pre8 -- reiserfs compilation errors
Date: 05 Jan 2002 00:52:22 -0800 [thread overview]
Message-ID: <1010220743.21181.4.camel@stomata.megapathdsl.net> (raw)
gcc -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 -c -o procfs.o procfs.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/src/linux/fs/reiserfs'
#
# File systems
#
CONFIG_QUOTA=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
CONFIG_REISERFS_FS=y
CONFIG_REISERFS_CHECK=y
CONFIG_REISERFS_PROC_INFO=y
Gnu C 3.0.3
Gnu make 3.79.1
binutils 2.10.91.0.2
util-linux 2.11n
mount 2.11n
modutils 2.4.12
e2fsprogs 1.23
reiserfsprogs 3.x.0j
pcmcia-cs 3.1.22
PPP 2.4.0
isdn4k-utils 3.1pre1
Linux C Library 2.2.4
Dynamic linker (ldd) 2.2.4
Linux C++ Library 3.0.2
Procps 2.0.7
Net-tools 1.57
Console-tools 0.3.3
Sh-utils 2.0
reply other threads:[~2002-01-05 8:52 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=1010220743.21181.4.camel@stomata.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®