Created attachment 224852 [details] Patch ports tree (-p0) Moinmoin, after brief email discussion with joerg@, kde@ would like an exp-run of an update to devel/gnulibiberty and devel/libbfd. This makes those two ports match the version of devel/binutils. Patch against the git ports tree is attached, use `-p0`. There don't seem to be many direct consumers of these two ports -- maybe everyone is using the more up-to-date binutils anyway -- and the patch fixes the only direct one that fails that I could find.
If there are no consumers, why the exp-run request? Just test build the two ports.
Good point, Mat. I just get cautious when dealing with things that seem to be "low" in the software stack. However, FreshPorts tells me that there *really* are no more consumers, so I'll un-tag exp-run and just commit after another round of test-builds.
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=47e21b774a21876aa848b7f69280715672ae8d6c commit 47e21b774a21876aa848b7f69280715672ae8d6c Author: Adriaan de Groot <adridg@FreeBSD.org> AuthorDate: 2021-05-10 14:11:57 +0000 Commit: Adriaan de Groot <adridg@FreeBSD.org> CommitDate: 2021-05-11 18:45:57 +0000 devel/gnulibiberty: bring up-to-date wrt devel/binutils Match the versions of libiberty and binutils. These come from the same tarball upstream, so it's a bit odd to have mismatched versions to start with; in addition the libiberty version is years out-of-date. While here, drop a CONFLICTS line that doesn't make sense anymore. PR: 255794 Approved by: joerg@ (maintainer) devel/gnulibiberty/Makefile | 7 ++--- devel/gnulibiberty/distinfo | 5 ++-- devel/gnulibiberty/files/patch-Makefile.in (gone) | 19 -------------- devel/gnulibiberty/files/patch-configure (gone) | 31 ----------------------- devel/gnulibiberty/pkg-plist | 1 + 5 files changed, 6 insertions(+), 57 deletions(-)