We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 4027

Summary: CheckLibSampleRate macro in sdlchecks.cmake never defines HAVE_LIBSAMPLERATE{,_SHARED}, so they're always reported as disabled by MESSAGE_TESTED_OPTION macro in macros.cmake
Product: SDL Reporter: Tiago O. <toacn-foss>
Component: buildAssignee: Sam Lantinga <slouken>
Status: RESOLVED ABANDONED QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2    
Version: HG 2.0   
Hardware: All   
OS: Linux   
Attachments: Add variables to indicate that samplerate was found

Description Tiago O. 2018-01-06 15:45:57 UTC
It only shows incorrect information, but doesn't really changes anything in the build process, as far as I've tested.
Comment 1 Sam Lantinga 2018-02-13 16:00:51 UTC
Do you have a tested patch to fix this?

Thanks!
Comment 2 Tiago O. 2018-02-13 16:37:38 UTC
Created attachment 3169 [details]
Add variables to indicate that samplerate was found

This will do the trick.
Comment 3 Sam Lantinga 2018-02-13 21:26:49 UTC
Fixed, thanks!
https://hg.libsdl.org/SDL/rev/c207c3ab46ee
Comment 4 Ryan C. Gordon 2018-08-06 21:20:20 UTC
Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.