From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] maxima-ecl: heap error on i686
Date: Tue, 11 Jan 2022 16:55:30 +0100 [thread overview]
Message-ID: <20220111155530.aRBnXEy9RwniO0TjbWM1jtUrnWfgi5TemXLuvBihUzE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34861@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
Closed issue by tornaria on void-packages repository
https://github.com/void-linux/void-packages/issues/34861
Description:
```
$ maxima -l ecll
;;; Loading #P"/usr/lib32/ecl-21.2.1/sb-bsd-sockets.fas"
;;; Loading #P"/usr/lib32/ecl-21.2.1/sockets.fas"
Maxima 5.45.1 https://maxima.sourceforge.io
using Lisp ECL 21.2.1
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
The function bug_report() provides bug reporting information.
(%i1) :lisp (ext:set-limit 'ext:heap-size 0)
0
(%i1) a : 10^(10^5) $ b : a^600 $ c : a^600 $
Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
Aborted
```
The first line sets `heap-size` to `0` meaning "no limit" (according to https://common-lisp.net/project/ecl/static/manual/Memory-Management.html#ext_003astorage_002dexhausted).
The same using maxima as compiled by sage works. The main difference between the two is that void's template sets `nopie=yes` , and a quick experiment seems to indicate that compiling pie will fix the issue.
The `nopie=yes` was set by https://github.com/void-linux/void-packages/commit/21173c2ce02bc9588b2de678ed1838882a8d0f1a but there is no explanation of the reason. @leahneukirchen do you remember?
prev parent reply other threads:[~2022-01-11 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 5:22 [ISSUE] " tornaria
2022-01-06 0:55 ` tornaria
2022-01-11 15:55 ` leahneukirchen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220111155530.aRBnXEy9RwniO0TjbWM1jtUrnWfgi5TemXLuvBihUzE@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).