From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: maxima fails to (natively) build using ecl
Date: Thu, 12 Oct 2023 22:13:06 +0200 [thread overview]
Message-ID: <20231012201306.38h6cbscWD7twBR6EqcPJG10aPrkMYrA8PVLn3OXOWM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46293@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1706 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/46293#issuecomment-1760304027
Comment:
No worries. Here 's my src/autoconf-variables.lisp:
```
$ cat masterdir/builddir/maxima-5.47.0/src/autoconf-variables.lisp
; -*- Lisp -*-
(in-package :maxima)
(defparameter *autoconf-prefix* "/usr")
(defparameter *autoconf-exec_prefix* "/usr")
(defparameter *autoconf-package* "maxima")
(defparameter *autoconf-version* "5.47.0")
(defparameter *autoconf-libdir* "/usr/lib64")
(defparameter *autoconf-libexecdir* "/usr/libexec")
(defparameter *autoconf-datadir* "/usr/share")
(defparameter *autoconf-infodir* "/usr/share/info")
(defparameter *autoconf-host* "x86_64-unknown-linux-gnu")
;; This variable is kept for backwards compatibility reasons:
;; We seem to be in the fortunate position that we sometimes need to check for windows.
;; But at least until dec 2015 we didn't need to check for a specific windows flavour.
(defparameter *autoconf-win32* "false")
(defparameter *autoconf-windows* "false")
(defparameter *autoconf-ld-flags* "-Wl,-z,relro -Wl,-z,now -Wl,--as-needed ")
;; This will be T if this was a lisp-only build
(defparameter *autoconf-lisp-only-build* (eq t 'nil))
(defparameter *maxima-source-root* "/builddir/maxima-5.47.0")
(defparameter *maxima-default-layout-autotools* "true")
```
Do you think it makes sense to also upstream this patch? https://github.com/void-linux/void-packages/blob/master/srcpkgs/maxima/patches/handle-multiple-ldflags.patch
Actually, could this patch be creating troubles? https://github.com/void-linux/void-packages/blob/master/srcpkgs/maxima/patches/use-shared-library.patch
next prev parent reply other threads:[~2023-10-12 20:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 15:28 [ISSUE] maxima fails to build natively on aarch64 dkwo
2023-09-29 13:44 ` dkwo
2023-09-29 13:45 ` dkwo
2023-10-02 21:51 ` dkwo
2023-10-03 0:12 ` tornaria
2023-10-03 14:22 ` dkwo
2023-10-11 22:13 ` maxima fails to build using ecl robert-dodier
2023-10-11 22:39 ` dkwo
2023-10-12 7:11 ` gunterkoenigsmann
2023-10-12 17:19 ` gunterkoenigsmann
2023-10-12 18:14 ` dkwo
2023-10-12 18:16 ` dkwo
2023-10-12 18:17 ` dkwo
2023-10-12 19:07 ` maxima fails to (natively) " dkwo
2023-10-12 19:24 ` dkwo
2023-10-12 19:48 ` robert-dodier
2023-10-12 19:51 ` robert-dodier
2023-10-12 20:13 ` dkwo [this message]
2023-10-12 20:27 ` dkwo
2023-10-12 21:03 ` dkwo
2023-10-13 10:58 ` tornaria
2023-10-14 19:48 ` dkwo
2023-10-16 3:00 ` robert-dodier
2023-10-16 18:01 ` [ISSUE] [CLOSED] " dkwo
2023-10-16 18:02 ` tornaria
2023-10-16 21:23 ` gunterkoenigsmann
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=20231012201306.38h6cbscWD7twBR6EqcPJG10aPrkMYrA8PVLn3OXOWM@z \
--to=dkwo@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).