When trying to emerge rubberband, the file "/usr/lib64/pkgconfig/vamp-sdk.pc" points to "${exec_prefix}/lib" instead of "${exec_prefix}/lib64", which results in make failing with "i386 architecture of input file `/var/tmp/portage/media-libs/rubberband-1.8.2/temp/vamp-rubberband.so.gDN8Du.ltrans0.ltrans.o' is incompatible with i386:x86-64 output", as the configuration script only looks in /usr/lib and completely overlooks /usr/lib64. Reproducible: Didn't try Steps to Reproduce: 1. Emerge vamp-plugin-sdk 2. Emerge rubberband Actual Results: The emerge of rubberband fails with "i386 architecture of input file `/var/tmp/portage/media-libs/rubberband-1.8.2/temp/vamp-rubberband.so.gDN8Du.ltrans0.ltrans.o' is incompatible with i386:x86-64 output" Expected Results: The emerge of rubberband finishes successfully. My exact profile is default/linux/amd64/17.1/desktop/plasma/systemd (stable). Though I have no doubt that this is in bad form, I shall link you to a forum thread by me regarding the issue: https://forums.gentoo.org/viewtopic-p-8354746.html I apologize for simply linking to a forum thread, but I have already documented this in good detail on there and have already spent far too long on this, considering that it is currently past three in the morning where I live, as well as there being other circumstances. I will, however, provide a few more details regarding this issue and summarize it as best as I am able to. I will hereon out assume that you have gone through the forum thread regarding the issue. I have just finished fighting with LibreOffice (GentooLTO stuff) and am two weeks behind on updates (emerge still ongoing as I type). After going over a few tickets on the GentooLTO GitHub, I was tweaking make.conf. Among other things, I decided to add ABI_X86="32 64", as I also needed to run a relatively old 32-bit version of Firefox (Java applet support). Afterwards, I ran "emerge --sync && emerge --verbose --deep --newuse --update @world && poweroff". When checking up on the laptop as it was going through 737 packages, I noticed vamp-plugin-sdk being emerged. It was innocuous at first, but it did pique my interest during the hunt for the problem with rubberband. At some point, after going over the thread once more, I thought about trying to see what can be done in /usr/lib64/pkgconfig/vamp-sdk.pc and, after seeing a clearly marked directory in the file, not to mention that it was a part of the libdir variable that I noticed during the configuration step after going over the output a few times, I got the idea to simply append "64" to that line. That fixed it for me. The only program to run concurrently with Konsole was Firefox Nightly (in /opt, not from a repository). I shall be attaching the emerge --info output shortly.
Created attachment 584464 [details] The promised emerge --info output
After reviewing my ticket, I have concluded that, while the fix is to simply add two numbers to the end of a line, it is still more than merely a minor issue. Also, I adjusted the title to make it a little more concise.
After running `emerge --verbose --emptytree @world`, I can confirm that this is reproducible.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e88a0ec57cb5d48f812bd036bdc14dbfc1de8f51 commit e88a0ec57cb5d48f812bd036bdc14dbfc1de8f51 Author: Miroslav Šulc <fordfrog@gentoo.org> AuthorDate: 2020-08-24 09:51:33 +0000 Commit: Miroslav Šulc <fordfrog@gentoo.org> CommitDate: 2020-08-24 09:51:49 +0000 media-libs/vamp-plugin-sdk: bump to 2.10 + fixed .pc files Closes: https://bugs.gentoo.org/690676 Package-Manager: Portage-3.0.4, Repoman-3.0.1 Signed-off-by: Miroslav Šulc <fordfrog@gentoo.org> media-libs/vamp-plugin-sdk/Manifest | 1 + .../vamp-plugin-sdk/vamp-plugin-sdk-2.10.ebuild | 74 ++++++++++++++++++++++ ....7.1.ebuild => vamp-plugin-sdk-2.7.1-r1.ebuild} | 3 + 3 files changed, 78 insertions(+)
