Using the LDFLAG --as-needed breaks compatibility with nvidia cards for this sensor reading program (its configure script to be more precise). This is only relevant when USE=nvidia is used. Using this LDFLAG results in: checking for XNVCTRLQueryExtension in -lXNVCtrl... no although it's there. Without you get: checking for XNVCTRLQueryExtension in -lXNVCtrl... yes Simply filtering the LDFLAG will do the job. I don't possess enough knowledge to determine if bug 207543 is related in any kind of way.
Fixed, thanks.
Closing, then :)
No this is NOT FIXED since it's just worked around in the tree.
Created attachment 180397 [details, diff] sensors-applet-2.2.1-nvidia-check.patch could you try this patch ?
Created attachment 180399 [details, diff] sensors-applet-2.2.1.ebuild.patch here is the ebuild patch. Since nvidia is proprietary crap, I don't want to impose eautoreconf on all users.
hey there, I really need this patch tested before I start to revert the fix in tree blindly and you complaining things broke again.
Oh, I'm sorry. I completely forgot about this bug :( Yes, I've tested the patches. The ebuild fails though. It tries to apply the patch before the sources are unpacked.
d'oh, my bad, could you put those lines in a src_unpack (and make sure to remove the append-ldflags line) ?
I'm sorry I couldn't figure this out, but in src_unpack emerge says "Unpacking Sources" and then proceeds to try to patch. So we still have no sources to base the patch on :( And what do you mean by remove append-ldflags? The ebuild-patch already did this :)
Created attachment 183465 [details] sensors-applet-2.2.1.ebuild.patch here is the updated ebuild patch, sorry for delay.
oops, you want to stick EAPI="2" before the inherit line too.
Created attachment 183469 [details] compilation output Ah, it was src_prepare. Should've tried that aswell :[ Well, okay. Both hunks in the patch fail for some reason, although I don't see why. So I patched by hand. Compilation fails tho (see attachment)
then that would be bug #207543. Thanks for testing, I'll include that to the tree as soon as possible (with a fix for the other bug if possible).
2.2.2 in tree with this fix. Thanks for testing. Please reopen if it's still an issue for you.