unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Kei Kebreau <kei@openmailbox.org>
To: 27628@debbugs.gnu.org
Subject: [bug#27628] Fix compilation features of GCL and Maxima
Date: Sat, 08 Jul 2017 21:12:26 -0400	[thread overview]
Message-ID: <87lgnyqupx.fsf@openmailbox.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 348 bytes --]

These patches are the best solution I've come upon so far to enable GCL
and Maxima to compile functions. The current issue is that GCL (and, by
proxy, Maxima) requires GCC to compile functions, but GCC and binutils
are not available to GCL at runtime. This issue in GCL causes issues in
Maxima (e.g. the graphing package "draw" does not function).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

             reply	other threads:[~2017-07-09  1:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-09  1:12 Kei Kebreau [this message]
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
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lgnyqupx.fsf@openmailbox.org \
    --to=kei@openmailbox.org \
    --cc=27628@debbugs.gnu.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).