|
[Sbcl-commits] master: Remove an OpenBSD note in the README which
is no longer necessary.
From: Joshua Elsasser <joshe@us...> - 2012-02-20 20:32
|
The branch "master" has been updated in SBCL:
via 622d651d974127e51598ef08c4a7d5bedd2575f5 (commit)
from cb1734df0f1d211b22071632e7278d8f278b8fe3 (commit)
- Log -----------------------------------------------------------------
commit 622d651d974127e51598ef08c4a7d5bedd2575f5
Author: Joshua Elsasser <joshua@...>
Date: Sun Feb 19 14:53:51 2012 -0800
Remove an OpenBSD note in the README which is no longer necessary.
OpenBSD's behavior has not changed, but the default SBCL allocation
size was changed some time ago to work with the default OpenBSD
resource limits.
---
README | 12 ------------
1 files changed, 0 insertions(+), 12 deletions(-)
diff --git a/README b/README
index 09984f3..7cc416d 100644
--- a/README
+++ b/README
@@ -33,15 +33,3 @@ SYSTEM-SPECIFIC HINTS
for NetBSD:
NetBSD 2.0 and above are required because of the lack of needed
signal APIs in NetBSD 1.6 and earlier.
-
-for OpenBSD:
- OpenBSD 3.0 has stricter ulimit values, and/or enforces them more
- strictly, than its predecessors. Therefore SBCL's initial mmap()
- won't work unless you increase the limit on the data segment from
- the OpenBSD defaults, e.g. with
- ulimit -S -d 1000000
- before you run SBCL. Otherwise SBCL fails with a message like
- "ensure_space: failed to validate xxxxxxx bytes at yyyyy". (SBCL
- is just allocating this huge address space, not actually using this
- huge memory at this point. OpenBSD <3.0 had no problem with this,
- but OpenBSD 3.0 is less hospitable.)
-----------------------------------------------------------------------
hooks/post-receive
--
SBCL
|
| Thread | Author | Date |
|---|---|---|
| [Sbcl-commits] master: Remove an OpenBSD note in the README which is no longer necessary. | Joshua Elsasser <joshe@us...> |