Opened 14 years ago
Last modified 5 years ago
#24944 assigned enhancement
ImageMagick 6.6.1-5_0 Need no-openmp variant
Reported by: | kingjc@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.8.2 |
Keywords: | openmp, haspatch | Cc: | snarkhunter (Steve Langer), felix.buenemann@…, rapkasta@…, dburry@…, wlipa (Bill Lipa), mmcmahand@…, jeff@… |
Port: | ImageMagick |
Description
Some software has conflicts with OpenMP when used with ImageMagick. In my case, the --disable-openmp option is needed when building ImageMagick to work with the OOF2 Finite Element Code (http://www.ctcms.nist.gov/oof/oof2/). Therefore, I suggesting the attached variant be added to ImageMagick.
Attachments (1)
Change History (13)
Changed 14 years ago by kingjc@…
Attachment: | Portfile-ImageMagick.diff added |
---|
comment:1 Changed 14 years ago by mf2k (Frank Schima)
Owner: | changed from macports-tickets@… to ryandesign@… |
---|
comment:2 Changed 14 years ago by wlipa (Bill Lipa)
Another use case that's going to become more common which triggers the problem is Ruby 1.9 / Rails / RMagick, I assume because of different threading model in Ruby 1.9.
See, for example: http://stackoverflow.com/questions/2838307/why-is-this-rmagick-call-generating-a-segmentation-fault and http://article.gmane.org/gmane.comp.lib.qt.general/26147
comment:3 Changed 14 years ago by jeff@…
This would also be huge for me and my workplace. We're having to patch this ourselves, currently.
comment:5 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Status: | new → assigned |
---|
comment:6 Changed 13 years ago by felix.buenemann@…
+1 openmp in ImageMagick 6.7.0 still causes ruby-1.9.2-p180 / rails 3.0.8 / rmagick 2.13.1 to segfault
comment:8 Changed 13 years ago by dburry@…
I've been maintaining my own private fork of this Portfile for 9 months due to this issue (6.6.5-6.7.2)... Being able to negate a default variant would work for me.
comment:9 follow-up: 10 Changed 12 years ago by wlipa (Bill Lipa)
After 2 years, it's still necessary to hand edit the Portfile in order to use ImageMagick with Rails / Ruby 1.9 and MacPorts without segmentation faults. That's a common scenario since popular file uploading gems rely on ImageMagick for thumbnail creation.
Can we please add the 3 lines to the ImageMagick portfile as in the supplied patch, to avoid all this hand editing?
comment:10 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | rapkasta@… dburry@… dojo@… mmcmahand@… jeff@… added |
---|
Has duplicate #35123.
Can we please add the 3 lines to the ImageMagick portfile as in the supplied patch, to avoid all this hand editing?
It's not quite as simple as that, considering comment:5 and #34231 and #34950.
I suppose I could make it as simple as just unconditionally turning off OpenMP support altogether, and dealing with the request of providing a variant to turn it back on (in supported configurations) later.
comment:11 Changed 12 years ago by wlipa (Bill Lipa)
I'm not following why it is not as simple as that, at least for a subset of users, since there are apparently many people that hand edit the file to manually add the variant.
Diff file with proposed variant