522984 – emerge should not unset user defined LD_PRELOAD

Bug 522984 - emerge should not unset user defined LD_PRELOAD

Summary: emerge should not unset user defined LD_PRELOAD

Status:	CONFIRMED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2014-09-17 06:39 UTC by octoploid
Modified:	2022-10-20 02:43 UTC (History)
CC List:	1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

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.