From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: maxima-ecl: heap error on i686
Date: Thu, 06 Jan 2022 01:55:12 +0100 [thread overview]
Message-ID: <20220106005512.ChOpFXwNESC4mCxXpeiBLkSQ08tbauhwuRaUtVmu7fc@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: 1117 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/issues/34861#issuecomment-1006197772
Comment:
> The `nopie=yes` was set by [21173c2](https://github.com/void-linux/void-packages/commit/21173c2ce02bc9588b2de678ed1838882a8d0f1a) but there is no explanation of the reason. @leahneukirchen do you remember?
I think I've figured this out.
- Regarding `nopie=yes`:
The building of maxima-sbcl using `--enable-sbcl-exec` produces a
nopie executable regardless of compilation flags.
Then the post-install hook `06-strip-and-debug-pkgs` will complain
that there is a nopie executable unless `nopie=yes`.
Alternative: use `nopie_files` to indicate this binary is nopie so the
other binaries are built pie and the current issue is solved.
- Regarding `nostrip=yes`:
The maxima-sbcl binary includes sbcl.core in such a way that stripping
will remove it -- the resulting binary won't work.
Alternative: use `nostrip_files` to skip stripping this binary.
Except `nostrip_files` doesn't take a full path, and all the binaries
are called `maxima`...
next prev parent reply other threads:[~2022-01-06 0: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 [this message]
2022-01-11 15:55 ` [ISSUE] [CLOSED] " leahneukirchen
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=20220106005512.ChOpFXwNESC4mCxXpeiBLkSQ08tbauhwuRaUtVmu7fc@z \
--to=tornaria@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).