Bug 522984

Summary:	emerge should not unset user defined LD_PRELOAD
Product:	Portage Development	Reporter:	octoploid <octoploid>
Component:	Unclassified	Assignee:	Portage team <dev-portage>
Status:	CONFIRMED ---
Severity:	normal	CC:	octoploid
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description octoploid 2014-09-17 06:39:36 UTC

Currently portage unsets any user defined LD_PRELOAD in save-ebuild-env.sh.
But sys-apps/sandbox handles this case just fine in sandbox/sandbox.bashrc.

E.g., using "LD_PRELOAD=/usr/lib/libllalloc.so.1.3 emerge ..." will speed up
the build time of large C++ applications by 8-10%. 
(http://locklessinc.com/benchmarks_allocator.shtml)


Reproducible: Always

Comment 1 Zac Medico gentoo-dev

2014-09-17 17:54:30 UTC

I guess we can filter it inside __preprocess_ebuild_env instead, since that will eliminate any stale LD_PRELOAD values that may exist in environment.bz2 files.