Open Bug 479519 Opened 16 years ago Updated 2 years ago

SpiderMonkey should refuse to configure with --enable-jemalloc if it can't find jemalloc sources

Categories

(Firefox Build System :: General, defect)

Product:
Firefox Build System
Component:
General
Version:
Other Branch
Type:
defect

Tracking

(Not tracked)

People

(Reporter: jorendorff, Unassigned)

References

Details

No description provided.
The SpiderMonkey source tree shouldn't make assumptions about the layout of the containing tree.
Summary: SpiderMonkey should refuse to configure with --enable-jemalloc if $(topsrcdir)/memory/jemalloc doesn't exist → SpiderMonkey should refuse to configure with --enable-jemalloc if it can't find jemalloc sources
Blocks: 586962
Is this about the _location_ of the sources, or about the contents? As in, can we assume that only jemalloc from the Mozilla tree is permissible, but perhaps it can be located in a different part of the tree to simplify life for distributions? Or are we saying that spidermonkey should work with arbitrary jemalloc versions?
Product: Core → Firefox Build System
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.