emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#18221: closed (MIT/GNU Scheme fails to build on no


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#18221: closed (MIT/GNU Scheme fails to build on non-Intel platforms)
Date: Tue, 19 Feb 2019 22:51:02 +0000

Your message dated Tue, 19 Feb 2019 23:50:48 +0100
with message-id <address@hidden>
and subject line Close
has caused the debbugs.gnu.org bug report #18221,
regarding MIT/GNU Scheme fails to build on non-Intel platforms
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
18221: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18221
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Source of mit-scheme Date: Fri, 8 Aug 2014 09:47:57 +0200 User-agent: Mutt/1.5.23 (2014-03-12)
Hello,

mit-scheme fails to build on mips64el-linux, because specific source is not
downloaded for this system. Furthermore, I wonder if in the corresponding
lines
  (match (%current-system)
    ("x86_64-linux" "x86-64")
    ("i686-linux" "i386")
    (_ "c"))
one need not also check for the target system in the usual manner.
Here the "c" should be the empty string, I think, and the preceding "-"
should be included into "x86-64" and "i386".

As the source field is set to #f, the command
  guix build mit-scheme -S
fails with a confusing error message.

Is all this worth it, or should we not revert to a generic build recipe?

Andreas




--- End Message ---
--- Begin Message --- Subject: Close Date: Tue, 19 Feb 2019 23:50:48 +0100 User-agent: Mutt/1.11.2 (2019-01-07)
The bug stricto sensu has been fixed by a "supported systems" clause.
Since in more than 4 years nobody seems to have missed the package on
other architectures, I am closing the bug for now.

Andreas



--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]