Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

4.1.0 is broken on i386: unknown type name 'intptr_t'; did you mean '__intptr_t'? #1081

Closed
yurivict opened this issue Aug 3, 2022 · 4 comments

Comments

@yurivict
Copy link

yurivict commented Aug 3, 2022

Describe the bug

/wrkdirs/usr/ports/audio/muse-sequencer/work/muse-4.1.0/src/al/dsp.cpp:52:20: error: unknown type name 'intptr_t'; did you mean '__intptr_t'?
            if ( ((intptr_t)buf % 16) != 0) {
                   ^~~~~~~~
                   __intptr_t
/usr/include/x86/_types.h:91:19: note: '__intptr_t' declared here
typedef __int32_t       __intptr_t;
                        ^
/wrkdirs/usr/ports/audio/muse-sequencer/work/muse-4.1.0/src/al/dsp.cpp:60:20: error: unknown type name 'intptr_t'; did you mean '__intptr_t'?
            if ( ((intptr_t)buf % 16) != 0) {
                   ^~~~~~~~
                   __intptr_t
/usr/include/x86/_types.h:91:19: note: '__intptr_t' declared here
typedef __int32_t       __intptr_t;
                        ^
/wrkdirs/usr/ports/audio/muse-sequencer/work/muse-4.1.0/src/al/dsp.cpp:69:20: error: unknown type name 'intptr_t'; did you mean '__intptr_t'?
            if ( ((intptr_t)dst & 15) != 0)
                   ^~~~~~~~

Desktop (please complete the following information):

  • OS: FreeBSD 13.1

clang-14

@terminator356
Copy link
Member

Hi. Someone fixed this 3 months ago, in pull request 1067.
The fix was simply to un-comment line 24, where stdint.h is included.

But be aware, these SSE routines are not used currently, they have needed
some attention and care for a long time.
They are supposed to be for optimizing our audio processing, but we don't use them right now.

@yurivict
Copy link
Author

yurivict commented Aug 3, 2022

I see. So maybe i386 would get fixed with the next release.

@terminator356
Copy link
Member

Yes it would appear so.

@terminator356
Copy link
Member

Hi, I'll close this for now, please re-open if anything further.
Thanks.
T.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants