Opened 10 years ago
Closed 10 years ago
#46567 closed defect (duplicate)
mozjs17 @17.0.0 does not build on Tiger
| Reported by: | csanchezdll | Owned by: | juanrgar@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.3 |
| Keywords: | haspatch tiger | Cc: | dbevans (David B. Evans), potmj (Michael Pot), ryandesign (Ryan Carsten Schmidt) |
| Port: | mozjs17 |
Description
Already reported on #45832, but I cleaned up the report and added some references.
- mozjs17 blacklists all gcc* compilers, so clang is the only option. But clang does not compiler on Tiger (and possibly on Leopard) at least on PPC (and probably won't as support seems to be dropped). Blacklisting all gccs is overkill.
According to https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/Build_Documentation clang is recommended if gcc fails (they do not give more information), but from http://mail-archives.apache.org/mod_mbox/couchdb-dev/201303.mbox/%3CCAJNb-9r3PGV-igeE9MU9wTLuzomt%2Bdrn62mhku8%2Bp7vxGMXfbg%40mail.gmail.com%3E I understand is the LLVM-backed gcc versions that fail only (that is, it can be compiled with pure gcc *or* with llvm+clang).
Patch blacklists only llvm-gcc.
- _SC_NPROCESSORS_ONLN is documented on 10.4 sysconf(3), but is not really present on unistd.h until Leopard.
Patch assumes one processor in Tiger.
Attachments (3)
Change History (8)
Changed 10 years ago by csanchezdll
| Attachment: | Portfile.diff added |
|---|
Changed 10 years ago by csanchezdll
| Attachment: | patch-js-src-jsgc.cpp.diff added |
|---|
Changed 10 years ago by csanchezdll
| Attachment: | patch-mfbt-double-conversion-utils.h.diff added |
|---|
comment:1 Changed 10 years ago by csanchezdll
| Cc: | csanchezdll@… added |
|---|
comment:2 Changed 10 years ago by mf2k (Frank Schima)
| Cc: | devans@… added; csanchezdll@… removed |
|---|---|
| Keywords: | tiger added |
| Owner: | changed from macports-tickets@… to juanrgar@… |
In the future, please Cc the port maintainers (port info --maintainers mozjs17), if any. As reporter, you do not need to Cc yourself.
comment:3 Changed 10 years ago by csanchezdll
Sorry about the Cc'ing port maintainters, I missed that paragraph on the Bug Reporting Guide. I will do in the future. I Cc'ed myself by mistake (wanted to follow other ticket but clicked wrong window) and I could now find a way to delete myself from Cc list afterwards.
comment:4 Changed 10 years ago by potmj (Michael Pot)
| Cc: | fmw@… added |
|---|
Cc Me[[BR]]
Confirm also broken on 10.5.8 intel.
Found as dependency upgrading wine-devel
comment:5 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
Thanks. I'll get this taken care of in the original ticket.
Cc Me!