From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: problem building perf
Date: Fri, 31 Jan 2020 14:52:01 +1100 [thread overview]
Message-ID: <20200131145201.422b6fb4@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1785 bytes --]
Hi all,
This morning trying to do a native perf build (powerpcle) produced
these errors:
util/srcline.c: In function 'find_address_in_section':
util/srcline.c:200:7: error: implicit declaration of function 'bfd_get_section_flags'; did you mean 'bfd_set_section_flags'? [-Werror=implicit-function-declaration]
200 | if ((bfd_get_section_flags(abfd, section) & SEC_ALLOC) == 0)
| ^~~~~~~~~~~~~~~~~~~~~
| bfd_set_section_flags
util/srcline.c:200:7: error: nested extern declaration of 'bfd_get_section_flags' [-Werror=nested-externs]
util/srcline.c:204:8: error: implicit declaration of function 'bfd_get_section_vma'; did you mean 'bfd_set_section_vma'? [-Werror=implicit-function-declaration]
204 | vma = bfd_get_section_vma(abfd, section);
| ^~~~~~~~~~~~~~~~~~~
| bfd_set_section_vma
util/srcline.c:204:8: error: nested extern declaration of 'bfd_get_section_vma' [-Werror=nested-externs]
util/srcline.c:205:9: error: implicit declaration of function 'bfd_get_section_size'; did you mean 'bfd_set_section_size'? [-Werror=implicit-function-declaration]
205 | size = bfd_get_section_size(section);
| ^~~~~~~~~~~~~~~~~~~~
| bfd_set_section_size
util/srcline.c:205:9: error: nested extern declaration of 'bfd_get_section_size' [-Werror=nested-externs]
I traced it back to an update to binutils-dev I did last night :-( The
update was from 2.33.1 to 2.33.90.20200122 on my Debian build machine.
The above three macros no longer appear anywhere in /usr/include
(they were in /usr/include/bfd.h before the upgrade). I have backed
the upgrade out for now.
I am wondering if this is a perf bug or a bintuils bug or a Debian
packaging bug?
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2020-01-31 3:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200131145201.422b6fb4@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=acme@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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).