-
Notifications
You must be signed in to change notification settings - Fork 181
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
ChannelStatistics breaks the cgo #301
Comments
The only useful information I could find on
It doesn't seem that any of the Imagick binding code is actually using |
Yes, I've also reached to that google group post while I'm looking for a solution and also this (https://tip.golang.org/src/cmd/cgo/internal/testerrors/testdata/issue28069.go) which is related to the issue in golang side. If there is no usage for that, I'll remove it and may be you can also put _ (underscore) to the file to omit from the compilation and create a new release so I can continue to use your repo other than my fork to have the future updates in your releases... thank you for your quick response. |
I've tagged this fix as v3.5.1 |
Ah ... I changed my program for three days. For three days I could die. |
Hello,
When I use imagemagick 7.1.1-24 or higher. I'm getting this compile error
cgo: ../../../../../../../../imagick/imagick/channel_statistics.go:16:6: unexpected: 16-byte float type - long double
Because of this commit in imagemagick
ImageMagick/ImageMagick@1f241fd
that contains long double variable additions in ChannelStatistics (long double - that is not precisely defined in golang).
Do you have any idea to get over it? It is a long time problem for me when I use golang with C integration and I couldn't find any solution to fix the long double variable usage.
I'm able to compile the golang application if I convert long double variables to double in statistics.h file in imagemagick header file and it will be mapped to float64 in golang. I couldn't have done any deep test if it is working but I believe, it will not break something. However, it is not a proper solution and I'm looking for a solution out of the box.
Thanks.
The text was updated successfully, but these errors were encountered: