Description of problem: I'm unable to build memstomp. I've tried: * On Arch Linux: cloning the repo, autoreconf -fiv, ./configure, changing libiberty.h include to libiberty/libiberty.h, make. I get a lot of errors. They are not resolved if I try the patches from the Fedora package. See first attachment. * On Fedora 21 alpha: rebuilding the RPM with the spec file from git master (http://pkgs.fedoraproject.org/cgit/memstomp.git/) fails with "configure: error: *** libiberty not found" even though I do have binutils-devel installed. See second attachment. Version-Release number of selected component: 0.1.4-14.fc21
Created attachment 947230 [details] Build on Arch Linux
Created attachment 947231 [details] Build on Fedora 21
If you could attach the config.log file from your attempted build on F21 it would be appreciated as that should point us to precisely why the configure script thought libiberty was unavailable. I'll note that builds for F21 and Rawhide are working fine. Those builds occur within koji/mock which provides a minimal and reproducible build environment. That would seem to indicate that whatever bits are on your arch linux or F21 systems are in some significant way different than what's in the F21 and Rawhide buildroots.
My fedora 21 alpha virtual machine wouldn't boot anymore for an unknown reason, so I've restarted from scratch and now it builds on Fedora 21. I've found the difference between Arch and Fedora: * on Fedora /usr/include/libiberty.h and /usr/lib64/libiberty.a come from binutils-devel-2.24-21.fc21.x86_64 * on Arch /usr/include/libiberty/libiberty.h and /usr/lib/libiberty.a come from gcc-4.9.1-2 And the libiberty version from gcc-4.9.1 has been imported in the binutils tree after the 2.24 release apparently: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=history;f=include/libiberty.h;h=bcc1f9afaf7b731f486b752f0f42578e44455223;hb=HEAD Thus this works with the "old" version from binutils on Fedora but fails with the "new" version from gcc on Arch. So I guess this is a heads-up to warn you that things will break with the next release of binutils :).
Thanks for the heads-up. binutils-2.25 is due real soon now and we'll be dropping it into rawhide shortly after the release and we'll clearly have to address whatever incompatbility creeped into libiberty at that point.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.