From: "slyfox at inbox dot ru" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/23914] New: Add --disable-werror to ./configure support (example trigger: CFLAGS=-Og
Date: Fri, 23 Nov 2018 16:29:00 -0000 [thread overview]
Message-ID: <bug-23914-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=23914
Bug ID: 23914
Summary: Add --disable-werror to ./configure support (example
trigger: CFLAGS=-Og
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: general
Assignee: unassigned at sourceware dot org
Reporter: slyfox at inbox dot ru
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
Initially I attempted to reproduce https://bugs.gentoo.org/671650 on vanilla
master on elfutils as:
$ autoreconf -i -f && ./configure --disable-maintainer-mode CFLAGS=-Og &&
make && make check
The problem is in unconditional -Werror addition in
config/eu.am: $(if $($(*F)_no_Werror),,-Werror) \
May I ask to add --disable-werror support to ./configure? That way elfutils
will be less dependent on exact toolchain version and compiler flags
(specifically warning flags).
Example failure:
dwarf_child.c: In function '__libdw_find_attr':
dwarf_child.c:99:10: error: 'readp' may be used uninitialized in this
function [-Werror=maybe-uninitialized]
readp += len;
^~
Today Gentoo crudely works it around by sed'ing out -Werror at build time:
https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-libs/elfutils/elfutils-0.175.ebuild#n34
sed -i 's:-Werror::' */Makefile.in || die
Thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-11-23 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 16:29 slyfox at inbox dot ru [this message]
2018-11-23 20:25 ` [Bug general/23914] " mark at klomp dot org
2018-11-23 23:42 ` slyfox at inbox dot ru
2018-11-28 13:41 ` mark at klomp dot org
2018-12-02 23:41 ` slyfox at inbox dot ru
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=bug-23914-10460@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).