build/SConscript.main - Issue 9463: Serialize links on Linux. Should fix http://code.google.com/p/chromium/issue...

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: build/SConscript.main

Issue 9463: Serialize links on Linux. Should fix http://code.google.com/p/chromium/issue... (Closed) Base URL: svn://chrome-svn/chrome/trunk/src/

Patch Set: '' Created 12 years, 1 month ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

Index: build/SConscript.main

===================================================================

--- build/SConscript.main (revision 4895)

+++ build/SConscript.main (working copy)

@@ -459,6 +459,10 @@

)

linux_env.Replace(

+ # Linking of large files uses lots of RAM, so serialize links

+ # using the handy flock command from util-linux.

+ LINK = 'flock ' + linux_env['TARGET_ROOT'] + '/linker.lock ' + linux_env['LINK'],

Evan Martin 2008/11/10 22:00:16 I wonder if you can get away with the "$FOO" patte

# We have several cases where archives depend on each other in a cyclic

# fashion. (V8Bindings, libport and WebCore being the most significant

# example.) Since the GNU linker does only a single pass over the archives

« no previous file with comments | « no previous file | no next file » | no next file with comments »