From: Lars Marowsky-Bree <lmb@suse.de>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] Compile fix for 0.8
Date: Mon, 21 Feb 2005 17:01:46 +0100 [thread overview]
Message-ID: <20050221160146.GH7016@marowsky-bree.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 472 bytes --]
The attached patch fixes a minor problem when compiling drbd-0.8:
linux/fs.h pulls in linux/wait.h via some nested includes, in which
P_ALL etc are #defines. Later, we try to include sys/wait.h, in which
P_ALL etc are enum names, and gcc doesn't like numeric enums.
Fix: simply include correct header.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business
[-- Attachment #2: drbd-08 --]
[-- Type: text/plain, Size: 413 bytes --]
Index: user/drbdmeta.c
===================================================================
--- user/drbdmeta.c (revision 1763)
+++ user/drbdmeta.c (working copy)
@@ -40,7 +40,7 @@
#include <unistd.h>
#include <fcntl.h>
-#include <linux/fs.h> /* for BLKGETSIZE64 */
+#include <sys/mount.h> /* for BLKGETSIZE64 */
#include <linux/drbd.h> /* only use DRBD_MAGIC from here! */
#include "drbdtool_common.h"
reply other threads:[~2005-02-21 16:01 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=20050221160146.GH7016@marowsky-bree.de \
--to=lmb@suse.de \
--cc=drbd-dev@lists.linbit.com \
/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