Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] [RFC] environment/configure/hardening: add -Werror=implicit.
Date: Tue, 02 Feb 2021 21:14:13 +0100	[thread overview]
Message-ID: <20210202201413.Bp9fLcZBHpN93NAQgUjoHsuq--Vj1zjWeLOu-eBR8ew@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28389@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1819 bytes --]

There is an updated pull request by ericonr against master on the void-packages repository

https://github.com/ericonr/void-packages werror
https://github.com/void-linux/void-packages/pull/28389

[RFC] environment/configure/hardening: add -Werror=implicit.
Warnings for implicit function definitions should be errors, since they
can lead to issues down the line when the implicit type rules get things
wrong, especially with variadic functions.

<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/28389.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-werror-28389.patch --]
[-- Type: text/x-diff, Size: 920 bytes --]

From c80e97f74da3d1311f3b921ae7d8eb3010b6e206 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=89rico=20Rolim?= <erico.erc@gmail.com>
Date: Mon, 1 Feb 2021 12:14:28 -0300
Subject: [PATCH] environment/configure/hardening: add
 -Werror=implicit-function-declaration.

Warnings for implicit function declarations should be errors, since they
can lead to issues down the line when the implicit type rules get things
wrong, especially with variadic functions.
---
 common/environment/configure/hardening.sh | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/common/environment/configure/hardening.sh b/common/environment/configure/hardening.sh
index 9e02364f2a1..025bb153183 100644
--- a/common/environment/configure/hardening.sh
+++ b/common/environment/configure/hardening.sh
@@ -28,3 +28,5 @@ else
 	FFLAGS="-fno-PIE ${FFLAGS}"
 	LDFLAGS="-no-pie ${LDFLAGS}"
 fi
+
+CFLAGS="${CFLAGS} -Werror=implicit-function-declaration"

  parent reply	other threads:[~2021-02-02 20:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 15:16 [PR PATCH] " ericonr
2021-02-01 15:24 ` [PR REVIEW] " sgn
2021-02-01 15:30 ` ericonr
2021-02-02 20:14 ` ericonr [this message]
2021-03-24  3:55 ` ericonr
2021-03-24 23:52 ` sgn
2021-03-25  0:03 ` ericonr
2021-06-10 16:44 ` [PR PATCH] [Updated] " ericonr
2021-06-10 17:20 ` ericonr
2022-05-03  2:13 ` github-actions
2022-05-17  2:14 ` [PR PATCH] [Closed]: " github-actions

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=20210202201413.Bp9fLcZBHpN93NAQgUjoHsuq--Vj1zjWeLOu-eBR8ew@z \
    --to=ericonr@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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;
as well as URLs for NNTP newsgroup(s).