Fixing incompatible pointer assignment that causes build on RHEL 10 t… #46
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…o fail
w/o this change, on RHEL 10, we get:
The reason this is necessary is as follows:
The implementation of the jpc_{ft,ns}_{synthesize,analyze} functions assume its
first argument is a pointer to jpc_fix_t, as all of them will copy it to a
local variable called startptr of this type. Because on some systems jpc_fix_t
is a long int, we might get a compilation error, as it happens on RHEL 10.
Change the type of the jpc_ft_synthesize argument so there is not an
incompatible pointer assignment. Changing the signature of
analyzeandsynthesizefields in the jpc_qmfb2d_t struct is also needed because theaforementioned functions will be assigned to them. Similarly,
jpc_tsfb_synthesize2() calls
synthesizebut mistakenly declares its forwardedargument as int*.
The same fix was applied as part of this commit: jasper-software/jasper@d743f7e in the upstream repository.
Once merged, could we make a new tag/released version?