mediea-sound/audacity-2.4.2-r1 failsat link time: '/usr/lib/gcc/x86_64-pc-linux-gnu/10.2.0/../../../../x86_64-pc-linux-gnu/bin/ld.gold: error: cannot find -lportsmf' This is despite the fact that the portsmf USE flag is not set: [ebuild U ] media-sound/audacity-2.4.2-r1::gentoo [2.3.3::gentoo] USE="alsa doc ffmpeg flac id3tag jack ladspa lame lv2 mad midi nls ogg%* portmidi%* portmixer sbsms soundtouch twolame vorbis vst -oss% -portsmf% -vamp (-libav%)" CPU_FLAGS_X86="sse" 0 KiB Reproducible: Always
Fine here: Installed versions: 2.4.2-r1(13:56:50 03/08/2020)(ffmpeg flac id3tag jack ladspa lv2 mad nls portmixer vamp vorbis vst -alsa -doc -lame -midi -ogg -oss -portmidi -portsmf -sbsms -soundtouch -twolame CPU_FLAGS_X86="sse")
(In reply to CaptainBlood from comment #1) > Fine here: > Installed versions: 2.4.2-r1(13:56:50 03/08/2020)(ffmpeg flac id3tag jack > ladspa lv2 mad nls portmixer vamp vorbis vst -alsa -doc -lame -midi -ogg > -oss -portmidi -portsmf -sbsms -soundtouch -twolame CPU_FLAGS_X86="sse") Thanks for the information. However, my point was really about the fact that media-sound/audacity-2.4.2-r1 fails to emerge with portmidi enabled and portsmf disabled. As it happens, this version of audacity emerges fine for me with these two USE flags either both set or both unset (the latter being your situation). As enabling portsmf doesn't appear to pull in any other dependencies and as there is presumably a close functionality between the two, I imagine there is arguably a case for either merging the two flags, or else forcing portsmf if portmidi is set.
Thank you for the report. We need to have all information at hand before ticket assignment. That is why I ask you to * attach the logs and * paste the emerge info as described on https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket Please reopen this ticket (Status:UNCONFIRMED) afterwards.
(In reply to Jonas Stein from comment #3) > Thank you for the report. We need to have all information at hand before > ticket assignment. That is why I ask you to > * attach the logs and > * paste the emerge info > as described on > https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket > Please reopen this ticket (Status:UNCONFIRMED) afterwards. Thanks for the response. Filing the bug was more of a heads-up indicating the need for a look at the USE flag combinations by @dev, rather than a request for help as such. I see this morning that there have now been some changes and that the un-bumped ebuild has a different set of USE flags (including (-midi%*) - although not touching portmidi or portsmf). So, as there is obviously churn here, I am re-opening this bug as UNCONFIRMED so that it is more easily available to others who might have questions/problems in this area. Thanks.
(In reply to Jonas Stein from comment #3) > Please reopen this ticket (Status:UNCONFIRMED) afterwards. Please stop doing that.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4ff643dc06f490e84c15930e4e091ac71148ebd0 commit 4ff643dc06f490e84c15930e4e091ac71148ebd0 Author: Miroslav Šulc <fordfrog@gentoo.org> AuthorDate: 2020-08-06 07:33:06 +0000 Commit: Miroslav Šulc <fordfrog@gentoo.org> CommitDate: 2020-08-06 07:33:27 +0000 media-sound/audacity: portmidi use flag requires portsmf in 2.4.2-r1 Closes: https://bugs.gentoo.org/735668 Package-Manager: Portage-3.0.1, Repoman-2.3.23 Signed-off-by: Miroslav Šulc <fordfrog@gentoo.org> media-sound/audacity/audacity-2.4.2-r1.ebuild | 2 ++ 1 file changed, 2 insertions(+)
