From: Hannes Reinecke <hare@suse.de>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: Mathieu Trudel-Lapierre <mathieu.trudel-lapierre@canonical.com>,
Dragan Stancevic <dragan.stancevic@canonical.com>,
device-mapper development <dm-devel@redhat.com>,
Ritesh Raj Sarraf <rrs@debian.org>,
Louis Bouchard <louis.bouchard@canonical.com>
Subject: Re: [PATCH 2/3] multipath-tools: merge OPTFLAGS into CFLAGS
Date: Fri, 15 Jul 2016 12:19:58 +0200 [thread overview]
Message-ID: <2af5e805-8bfe-72dc-d476-1c0184b76720@suse.de> (raw)
In-Reply-To: <1467995301-14226-3-git-send-email-xose.vazquez@gmail.com>
On 07/08/2016 06:28 PM, Xose Vazquez Perez wrote:
> OPTFLAGS is not used anywhere, but maybe it's intrusive for distributions.
>
> Cc: Mathieu Trudel-Lapierre <mathieu.trudel-lapierre@canonical.com>
> Cc: Dragan Stancevic <dragan.stancevic@canonical.com>
> Cc: Louis Bouchard <louis.bouchard@canonical.com>
> Cc: Ritesh Raj Sarraf <rrs@debian.org>
> Cc: Benjamin Marzinski <bmarzins@redhat.com>
> Cc: Hannes Reinecke <hare@suse.de>
> Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>
> Cc: device-mapper development <dm-devel@redhat.com>
> Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
> ---
> Makefile.inc | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/Makefile.inc b/Makefile.inc
> index 01d743c..b7077fc 100644
> --- a/Makefile.inc
> +++ b/Makefile.inc
> @@ -60,10 +60,9 @@ RM = rm -f
> LN = ln -sf
> INSTALL_PROGRAM = install
>
> -OPTFLAGS = -Wunused -Wstrict-prototypes -O2 -g -pipe -Wformat-security -Wall \
> - -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4
> -
> -CFLAGS = $(OPTFLAGS) -fPIC -DLIB_STRING=\"${LIB}\" -DRUN_DIR=\"${RUN}\"
> +CFLAGS = -Wunused -Wstrict-prototypes -O2 -g -pipe -Wformat-security -Wall \
> + -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 \
> + -fPIC -DLIB_STRING=\"${LIB}\" -DRUN_DIR=\"${RUN}\"
> SHARED_FLAGS = -shared
>
> %.o: %.c
>
Nope, doesn't work for us.
Our buildsystem is using a distinct set of flags, which we need to use
for the build process.
At the same time we have no idea if there are other flags (like includes
etc) which are required by the build itself.
Please revert, this breaks our build.
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2016-07-15 10:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 16:28 [PATCH 0/3] Makefiles housekeeping III Xose Vazquez Perez
2016-07-08 16:28 ` [PATCH 1/3] multipath-tools: install libs in a standard way Xose Vazquez Perez
2016-07-08 16:28 ` [PATCH 2/3] multipath-tools: merge OPTFLAGS into CFLAGS Xose Vazquez Perez
2016-07-09 9:19 ` Ritesh Raj Sarraf
2016-07-15 10:19 ` Hannes Reinecke [this message]
2016-07-22 9:43 ` Christophe Varoqui
2016-07-08 16:28 ` [PATCH 3/3] multipath-tools: delete INSTALL_PROGRAM from libmpathpersist/Makefile Xose Vazquez Perez
2016-07-09 8:04 ` [PATCH 0/3] Makefiles housekeeping III Christophe Varoqui
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=2af5e805-8bfe-72dc-d476-1c0184b76720@suse.de \
--to=hare@suse.de \
--cc=dm-devel@redhat.com \
--cc=dragan.stancevic@canonical.com \
--cc=louis.bouchard@canonical.com \
--cc=mathieu.trudel-lapierre@canonical.com \
--cc=rrs@debian.org \
--cc=xose.vazquez@gmail.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.