Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 611204

Summary: dev-lang/spidermonkey-45.0.2 buglet and file collisions
Product: Gentoo Linux Reporter: Helmut Jarausch <jarausch>
Component: Current packagesAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED FIXED    
Severity: normal CC: atoth
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Helmut Jarausch 2017-02-28 11:50:26 UTC
First, I got
sed: character class syntax is [[:space:]], not [:space:]
configure: error: cannot determine icu version number from uvernum.h header file 

which I patched with
--- js/src/configure.ORIG	2016-04-14 19:58:48.000000000 +0200
+++ js/src/configure	2017-02-28 12:48:38.511003635 +0100
@@ -15906,7 +15906,7 @@
         fi
     fi
 
-    version=`sed -n 's/^[:space:]*#[[:space:]]*define[[:space:]][[:space:]]*U_ICU_VERSION_MAJOR_NUM[[:space:]][[:space:]]*\([0-9][0-9]*\)[[:space:]]*$/\1/p' "$icudir/common/unicode/uvernum.h"`
+    version=`sed -n 's/^[[:space:]]*#[[:space:]]*define[[:space:]][[:space:]]*U_ICU_VERSION_MAJOR_NUM[[:space:]][[:space:]]*\([0-9][0-9]*\)[[:space:]]*$/\1/p' "$icudir/common/unicode/uvernum.h"`
     if test x"$version" = x; then
        { echo "configure: error: cannot determine icu version number from uvernum.h header file $lineno" 1>&2; echo "configure: error: cannot determine icu version number from uvernum.h header file $lineno" 1>&5; exit 1; }
     fi



Then installation failed with file collisions:
 * dev-lang/spidermonkey-1.8.5-r6:0::gentoo
 *      /usr/bin/js
 *      /usr/bin/js-config
 *      /usr/lib/debug/usr/bin/js.debug
Comment 1 Ian Stakenvicius (RETIRED) gentoo-dev 2017-02-28 18:49:19 UTC
The collisions I have fixed with a separate commit, while doing a lot of cleanups and attempting to address bug 611176.  The sed issue has just been fixed as well via bug 611232.

If there are any other issues with spidermonkey:38 please file a new bug, though if you run across these same issues again please reopen.