From: Fabio Massimo Di Nitto <fabbione@ubuntu.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] Fix gnbd/server build warning
Date: Wed, 29 Aug 2007 09:24:53 +0200 [thread overview]
Message-ID: <46D51F45.1030106@ubuntu.com> (raw)
gcc -Wall -I/usr/src/ubuntu/mypkgs/rhcluster/cluster/config
-DRELEASE_VERSION=\"DEVEL.1188196448\" -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -I/usr/src/ubuntu/mypkgs/rhcluster/cluster/gnbd-kernel/src
-I/usr/src/ubuntu/mypkgs/rhcluster/cluster/cman/lib -I../include -I../utils
-I/usr/include -c -o gserv.o gserv.c
gserv.c:15:1: warning: "__USE_XOPEN2K" redefined
In file included from /usr/include/unistd.h:26,
from gserv.c:13:
/usr/include/features.h:218:1: warning: this is the location of the previous
definition
the patch in attachment will fix the warning and retain backwards compatibility.
Please apply or ACK.
Thanks
Fabio
--
I'm going to make him an offer he can't refuse.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: gnbd_server.diff
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20070829/9916eca3/attachment.ksh>
next reply other threads:[~2007-08-29 7:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 7:24 Fabio Massimo Di Nitto [this message]
2007-08-30 17:37 ` [Cluster-devel] [PATCH] Fix gnbd/server build warning Lon Hohberger
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=46D51F45.1030106@ubuntu.com \
--to=fabbione@ubuntu.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.