1379537 - Standalone SpiderMonkey should copy headers on `make install` instead of symlinking

Status: RESOLVED FIXED

(Core :: JavaScript Engine, defect)

Description

[Philip Chimento [:ptomato]]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce:

When building SpiderMonkey standalone, `make install` symlinks the header files into the install directories. This is incompatible with the way that GNOME and its various downstream packagers will need to build SpiderMonkey. Instead, the header files should be copied.


Actual results:

Installed files in $prefix/include/mozjs-52/ are all symlinks.


Expected results:

Installed files in $prefix/include/mozjs-52/ should not be symlinks.

Comment 1

[Philip Chimento [:ptomato]]

Attachment: build: Copy headers on install instead of symlinking

Here's a patch that works for me.

Comment 2

[Till Schneidereit [:till]]

Comment on attachment 8884715 [details] [diff] [review]
build: Copy headers on install instead of symlinking

Review of attachment 8884715 [details] [diff] [review]:
-----------------------------------------------------------------

Does this seem reasonable, or is something else required?

Comment 3

[Mike Hommey [:glandium]]

Comment on attachment 8884715 [details] [diff] [review]
build: Copy headers on install instead of symlinking

Review of attachment 8884715 [details] [diff] [review]:
-----------------------------------------------------------------

This changes more than advertized. As in the other bug, what you want is to change the behavior of make install, without touching what the normal build does.

Comment 4

[Philip Chimento [:ptomato]]

OK, found it - make install already does specify --no-symlinks to process_install_manifest.py, but the InstallManifestNoSymlinks class doesn't do the right thing for add_pattern_symlink().

Comment 5

[Philip Chimento [:ptomato]]

Attachment: Fix InstallManifestNoSymlinks to not install symlinks

Comment 6

[Ted Campbell [:tcampbell]]

Try run: https://treeherder.mozilla.org/#/jobs?repo=try&revision=cb488da4179f2b27f87cbdce66f1fdb872868f88

Comment 7

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/bbac1c606f3d
Fix InstallManifestNoSymlinks to not install symlinks. r=glandium

Comment 8

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/bbac1c606f3d

Comment 9

[Philip Chimento [:ptomato]]

Comment on attachment 8889015 [details] [diff] [review]
Fix InstallManifestNoSymlinks to not install symlinks

[Approval Request Comment]
If this is not a sec:{high,crit} bug, please state case for ESR consideration: Fixes a build problem that affects downstream packagers (Linux distributions) of SpiderMonkey ESR releases.
User impact if declined: None to Firefox users, but the SpiderMonkey standalone release will be less usable for embedders, and downstream packagers will have to maintain this patch themselves
Fix Landed on Version: 56
Risk to taking this patch (and alternatives if risky): None, it is my understanding that SpiderMonkey's `make install` is not used in Firefox's build process, only by SpiderMonkey embedders
String or UUID changes made by this patch: None 

See https://wiki.mozilla.org/Release_Management/ESR_Landing_Process for more info.

Comment 10

[Gerry Chang [:gchang]]

Comment on attachment 8889015 [details] [diff] [review]
Fix InstallManifestNoSymlinks to not install symlinks

Needed for spidermonkey. Let's uplift it to ESR52.3.

Comment 11

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/releases/mozilla-esr52/rev/fd052b08fc3e