Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 525522 - www-client/firefox-33.0 - .../work/mozilla-release/memory/jemalloc/src/configure contains bashisms
Summary: www-client/firefox-33.0 - .../work/mozilla-release/memory/jemalloc/src/config...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Mozilla Gentoo Team
URL:
Whiteboard:
Keywords: PATCH
Depends on:
Blocks:
 
Reported: 2014-10-15 19:38 UTC by Morris
Modified: 2015-04-06 17:56 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
example diff (firefox-33.0-ebuild.patch,494 bytes, patch)
2014-10-15 19:38 UTC, Morris
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Morris 2014-10-15 19:38:10 UTC
Created attachment 386740 [details, diff]
example diff

Please note that this is also very likely to be an upstream bug, due to '==' bash'isms in /var/tmp/portage/www-client/firefox-33.0/work/mozilla-release/memory/jemalloc/src/configure

A user patch would also work, but it is an trivial FIX with src_prepare():
sed -i 's/if test \(.*\) == /if test \1 = /' "${S}"/memory/jemalloc/src/configure

I'm attaching an example diff. Thanks in advance.
Comment 1 Morris 2014-10-15 19:51:38 UTC
Also reported to Mozilla's bugzilla:

https://bugzilla.mozilla.org/show_bug.cgi?id=1083406
Comment 2 Ian Stakenvicius (RETIRED) gentoo-dev 2014-10-16 13:52:37 UTC
Well this is a problem in general, as afaik firefox should be using the system-installed jemalloc in the first place.  I'll look into both.
Comment 3 Ian Stakenvicius (RETIRED) gentoo-dev 2014-10-16 21:12:16 UTC
Upstream has already fixed this, it might still be there in mozilla34 so i'll stay aware of it for that release.  Patched and committed the fix in-place.
Comment 4 Mikael Magnusson 2015-04-06 17:56:22 UTC
This bug is back, reported at bug #545756