From: ludo@gnu.org (Ludovic Courtès)
To: Kei Kebreau <kei@openmailbox.org>
Cc: 27628@debbugs.gnu.org
Subject: [bug#27628] [PATCH 3/3] gnu: maxima: Ensure gcc and binutils available at runtime.
Date: Wed, 12 Jul 2017 14:07:15 +0200 [thread overview]
Message-ID: <871splg8p8.fsf@gnu.org> (raw)
In-Reply-To: <20170709011634.12832-3-kei@openmailbox.org> (Kei Kebreau's message of "Sat, 8 Jul 2017 21:16:34 -0400")
Kei Kebreau <kei@openmailbox.org> skribis:
> + ;; Ensure that Maxima will have access to GCC and its required
> + ;; components at runtime.
In fact, if it’s an optional feature, it would be better to take GCC &
co. from $PATH, because GCC is a huge dependency. (Same for the gcl
change.)
Thoughts?
Ludo’.
next prev parent reply other threads:[~2017-07-12 12:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 1:12 [bug#27628] Fix compilation features of GCL and Maxima Kei Kebreau
2017-07-09 1:16 ` [bug#27628] [PATCH 1/3] gnu: gcl: Ensure gcc and binutils are available at runtime Kei Kebreau
2017-07-09 1:16 ` [bug#27628] [PATCH 2/3] Revert "gnu: maxima: Ensure gcc is available at runtime." Kei Kebreau
2017-07-12 12:05 ` Ludovic Courtès
2017-07-09 1:16 ` [bug#27628] [PATCH 3/3] gnu: maxima: Ensure gcc and binutils available at runtime Kei Kebreau
2017-07-12 12:06 ` Ludovic Courtès
2017-07-12 12:07 ` Ludovic Courtès [this message]
2017-07-12 23:31 ` Kei Kebreau
2017-07-17 8:19 ` Ludovic Courtès
2017-07-18 14:11 ` Kei Kebreau
2017-07-18 14:53 ` Ludovic Courtès
2017-07-18 22:10 ` Kei Kebreau
2017-07-18 23:34 ` Marius Bakke
2017-07-20 2:03 ` Kei Kebreau
2017-07-24 16:08 ` Kei Kebreau
2017-07-19 8:55 ` Ludovic Courtès
2017-07-25 13:13 ` bug#27628: " Kei Kebreau
2017-07-12 12:04 ` [bug#27628] [PATCH 1/3] gnu: gcl: Ensure gcc and binutils are " Ludovic Courtès
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=871splg8p8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27628@debbugs.gnu.org \
--cc=kei@openmailbox.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.