Opened 17 months ago
Last modified 10 months ago
#70455 assigned defect
mozjpeg: why x86-only?
| Reported by: | barracuda156 | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.9.3 |
| Keywords: | arm64 ppc | Cc: | |
| Port: | mozjpeg |
Description
The port builds as-is for ppc and even claims some altivec code. Nothing seems to suggest it should be Intel-only. README has some mentions of arm too.
Change History (5)
comment:1 follow-up: 3 Changed 16 months ago by raimue (Rainer Müller)
comment:2 Changed 16 months ago by raimue (Rainer Müller)
| Keywords: | arm64 ppc added |
|---|
comment:3 Changed 16 months ago by barracuda156
Replying to raimue:
As mozjpeg started as a fork of libjpeg-turbo, I assume it initially only supported x86. I do not have a change to test it on anything else, but it might well be that it supports other architectures.
I think arch restriction should be removed. It is clear that as of existing version it does support non-x86 archs. Being untested is not a reason to prohibit building.
comment:4 follow-up: 5 Changed 10 months ago by raimue (Rainer Müller)
| Owner: | raimue deleted |
|---|
Dropping maintainership of mozjpeg. Sorry, just being honest that I won't ever get to work on this.
comment:5 Changed 10 months ago by barracuda156
Replying to raimue:
Dropping maintainership of mozjpeg. Sorry, just being honest that I won't ever get to work on this.
No drama. If anyone bumps into this in the future, just drop restriction, it should build fine on ppc.
As mozjpeg started as a fork of libjpeg-turbo, I assume it initially only supported x86. I do not have a change to test it on anything else, but it might well be that it supports other architectures.