From: "Michael D. Crawford" <crawford@goingware.com>
To: linux-kernel@vger.kernel.org
Subject: Can't compile shmem.c in 2.4.0-ac9
Date: Tue, 16 Jan 2001 23:07:48 +0000 [thread overview]
Message-ID: <3A64D444.CDC7DEB5@goingware.com> (raw)
I get the following errors trying to build 2.4.0-ac9 just now.
I'll send you my .config upon request, or post it on my website
gcc -D__KERNEL__ -I/home/mike/Kernel/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686 -c -o shmem.o
shmem.c
shmem.c:971: `shmem_readlink' undeclared here (not in a function)
shmem.c:971: initializer element for `shmem_symlink_inode_operations.readlink'
is not constant
shmem.c:972: `shmem_follow_link' undeclared here (not in a function)
shmem.c:972: initializer element for
`shmem_symlink_inode_operations.follow_link' is not constant
shmem.c:973: initializer element for `shmem_symlink_inode_operations' is not
constant
shmem.c:973: initializer element for `shmem_symlink_inode_operations' is not
constant
make[2]: *** [shmem.o] Error 1
make[2]: Leaving directory `/home/mike/Kernel/linux/mm'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/home/mike/Kernel/linux/mm'
make: *** [_dir_mm] Er
Mike
--
Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
crawford@goingware.com
Tilting at Windmills for a Better Tomorrow.
-
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/
next reply other threads:[~2001-01-17 2:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 23:07 Michael D. Crawford [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-17 0:33 Can't compile shmem.c in 2.4.0-ac9 Michael D. Crawford
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=3A64D444.CDC7DEB5@goingware.com \
--to=crawford@goingware.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.