From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 4/4] make, travis: Remove -Werror-implicit-function-declaration
Date: Tue, 6 Aug 2019 18:48:40 +0200 [thread overview]
Message-ID: <20190806164840.GA29935@dell5510> (raw)
In-Reply-To: <20190802150445.10984-5-pvorel@suse.cz>
Hi,
> and add it to Travis CI builds.
> Previously it was passed only to Android build. Generally Werror flags
> should be on for development but disabled for releases and production.
> We don't have any configure flag stating development build, so using it
> only in Travis CI should be sufficient (although we lost lost this check
> for Android as we don't test it in our Travis CI setup).
> Suggested-by: Cyril Hrubis <chrubis@suse.cz>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> Travis build: https://travis-ci.org/pevik/ltp/builds/566982062
This one replaced by https://patchwork.ozlabs.org/patch/1142959/
Travis build: https://travis-ci.org/pevik/ltp/builds/568461383
Kind regards,
Petr
next prev parent reply other threads:[~2019-08-06 16:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 15:04 [LTP] [PATCH v2 0/4] Move -Werror-implicit-function-declaration to Petr Vorel
2019-08-02 15:04 ` [LTP] [PATCH v2 1/4] make: Remove C++ related flags Petr Vorel
2019-08-02 15:04 ` [LTP] [PATCH v2 2/4] utils/ffsb: Add missing fhstat() signature + includes Petr Vorel
2019-08-02 15:14 ` Cyril Hrubis
2019-08-02 15:31 ` Petr Vorel
2019-08-02 15:04 ` [LTP] [PATCH v2 3/4] build.sh: Respect user defined CFLAGS and LDFLAGS Petr Vorel
2019-08-02 15:04 ` [LTP] [PATCH v2 4/4] make, travis: Remove -Werror-implicit-function-declaration Petr Vorel
2019-08-06 16:48 ` Petr Vorel [this message]
2019-08-02 15:08 ` [LTP] [PATCH v2 0/4] Move -Werror-implicit-function-declaration to Petr Vorel
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=20190806164840.GA29935@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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.