Bug 202485 - lang/spidermonkey170 fail powerpc
Summary: lang/spidermonkey170 fail powerpc
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: powerpc Any
: --- Affects Only Me
Assignee: Koop Mast
URL:
Keywords:
: 202486 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-08-19 15:20 UTC by Roosevelt
Modified: 2015-10-17 19:47 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (kwm)

Attachments
error message of spidermonkey (5.38 KB, text/plain)
2015-08-19 15:20 UTC, Roosevelt 		no flags Details
Patch to remove the jsuword word from 64-bit BE jsval struct (306 bytes, patch)
2015-10-13 23:40 UTC, Justin Hibbits 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roosevelt 2015-08-19 15:20:39 UTC 
Created attachment 160105 [details]
error message of spidermonkey

Environment:
FreeBSD Current 11 ppc64


Description:
spidermonkey170 is a dep. of polkit(libmozjs-17.0.so). This build fail with the following attachment showing the discrepancy. I have tried spidermonkey185 with no avail. 


How to Repeat:
cd to lang/spidermonkey170 to make install.

Fix:
None tried spidermonkey17. But there is no libmozjs.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2015-08-19 15:31:16 UTC 
*** Bug 202486 has been marked as a duplicate of this bug. ***
Comment 2 Roosevelt 2015-08-20 14:54:56 UTC 
I was able to install lang/spidermonkey170 taking out jsuworld in the offending file /work/mozjs17.0.0/js/src/jsval.h.
Comment 3 Justin Hibbits freebsd_committer freebsd_triage 2015-10-13 23:40:15 UTC 
Created attachment 162003 [details]
Patch to remove the jsuword word from 64-bit BE jsval struct

spidermonkey builds with this patch on powerpc64.
Comment 4 Julio Merino,+1 347 694 0576,New York City freebsd_committer freebsd_triage 2015-10-17 19:47:51 UTC 
Incidentally, I fixed this yesterday in r399507.  I suspect the same patch should be applied to spidermonkey185 but I haven't tried yet.  Let's close this because the bug is about spidermonkey170.