From: Lars Marowsky-Bree <lmb@suse.de>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] Re: [DRBD-cvs] r1598 - trunk/user
Date: Tue, 19 Oct 2004 11:13:07 +0200 [thread overview]
Message-ID: <20041019091307.GD9603@marowsky-bree.de> (raw)
In-Reply-To: <20041019073224.518E93BE6D@garcon.linbit.com>
On 2004-10-19T09:32:24, svn@svn.drbd.org wrote:
> Author: phil
> Date: 2004-10-19 09:32:21 +0200 (Tue, 19 Oct 2004)
> New Revision: 1598
>
> Modified:
> trunk/user/Makefile
> trunk/user/drbdmeta.c
> Log:
> [patch by LGE]
> * removed the dependency on glib, and use the kernel's
> includes instead.
Do not do that. Please. Including kernel-headers from user-space is an
absolute nightmare, it keeps breaking sporadically and in particular on
non-i386 archs. The kernel headers just aren't meant to be used in
user-space (and are documented to not be supported for this), and all
the build issues I've had with OCFS, Lustre, ... have been caused by
this.
In particular these headers
> +#include <asm/byteorder.h> /* for the __cpu_to_le64 etc. functions */
> +#include <linux/bitops.h> /* for the hweight functions */
> +#include <linux/types.h> /* for the __u32/64 type defs */
_are known to break_ on ia64/ppc64/s390x. I'd be very grateful if you
could avoid this.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX AG - A Novell company
next parent reply other threads:[~2004-10-19 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041019073224.518E93BE6D@garcon.linbit.com>
2004-10-19 9:13 ` Lars Marowsky-Bree [this message]
2004-10-19 10:19 ` [Drbd-dev] Re: [DRBD-cvs] r1598 - trunk/user Lars Ellenberg
2004-10-19 10:43 ` Lars Ellenberg
2004-10-19 10:52 ` Philipp Reisner
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=20041019091307.GD9603@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 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.