From: "José María Alonso" <nimiux@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/lisp:master commit in: eclass/
Date: Tue, 22 Aug 2017 21:32:10 +0000 (UTC) [thread overview]
Message-ID: <1503437560.59492b860e673f1a301981554382934b36589545.nimiux@gentoo> (raw)
commit: 59492b860e673f1a301981554382934b36589545
Author: Chema Alonso Josa <nimiux <AT> gentoo <DOT> org>
AuthorDate: Tue Aug 22 21:32:40 2017 +0000
Commit: José María Alonso <nimiux <AT> gentoo <DOT> org>
CommitDate: Tue Aug 22 21:32:40 2017 +0000
URL: https://gitweb.gentoo.org/proj/lisp.git/commit/?id=59492b86
common-lisp-3.eclass: Updates header and CL_BINARY variable
eclass/common-lisp-3.eclass | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/eclass/common-lisp-3.eclass b/eclass/common-lisp-3.eclass
index d079e552..290b7532 100644
--- a/eclass/common-lisp-3.eclass
+++ b/eclass/common-lisp-3.eclass
@@ -1,6 +1,5 @@
-# Copyright 1999-2016 Gentoo Foundation
+# Copyright 1999-2017 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Id$
# @ECLASS: common-lisp-3.eclass
# @MAINTAINER:
@@ -42,7 +41,9 @@ EXPORT_FUNCTIONS src_compile src_install
# @DESCRIPTION:
# Since there's nothing to build in most cases, default doesn't do
# anything.
-common-lisp-3_src_compile() { true; }
+common-lisp-3_src_compile() {
+ true;
+}
# @FUNCTION: absolute-path-p
# @DESCRIPTION:
@@ -178,13 +179,14 @@ common-lisp-export-impl-args() {
die "${FUNCNAME[0]}: wrong number of arguments: $#"
fi
CL_BINARY="${1}"
- case ${1} in
+ case "${CL_BINARY}" in
clisp)
CL_NORC="-norc"
CL_LOAD="-i"
CL_EVAL="-x"
;;
- clozurecl | ccl | openmcl)
+ clozure | clozurecl | ccl | openmcl)
+ CL_BINARY="ccl"
CL_NORC="--no-init"
CL_LOAD="--load"
CL_EVAL="--eval"
@@ -206,7 +208,7 @@ common-lisp-export-impl-args() {
CL_EVAL="--eval"
;;
*)
- die ${1} is not supported by ${0}
+ die "${CL_BINARY} is not supported by ${0}"
;;
esac
export CL_BINARY CL_NORC CL_LOAD CL_EVAL
next reply other threads:[~2017-08-22 21:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 21:32 José María Alonso [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-16 18:19 [gentoo-commits] proj/lisp:master commit in: eclass/ Ulrich Müller
2023-06-16 10:42 Ulrich Müller
2022-04-03 17:56 Ulrich Müller
2022-04-01 11:12 Ulrich Müller
2022-03-26 17:29 Ulrich Müller
2022-03-24 6:54 Ulrich Müller
2022-03-13 20:27 Ulrich Müller
2022-03-13 20:21 Ulrich Müller
2020-02-11 21:25 Ulrich Müller
2019-08-08 21:24 Ulrich Müller
2019-08-08 21:24 Ulrich Müller
2018-06-21 14:40 José María Alonso
2018-05-31 16:10 José María Alonso
2018-05-31 16:08 José María Alonso
2018-05-19 14:01 José María Alonso
2018-05-18 19:56 José María Alonso
2018-03-17 21:30 José María Alonso
2017-12-10 19:56 José María Alonso
2017-10-28 14:29 José María Alonso
2017-10-28 14:27 José María Alonso
2017-10-28 14:25 José María Alonso
2017-10-06 21:21 José María Alonso
2017-08-29 15:23 José María Alonso
2017-08-22 21:36 José María Alonso
2017-08-22 21:33 José María Alonso
2017-08-22 21:28 José María Alonso
2016-11-30 14:25 José María Alonso
2016-11-29 22:43 José María Alonso
2016-06-17 16:01 José María Alonso
2015-08-18 21:24 José María Alonso
2013-04-04 19:10 Stelian Ionescu
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=1503437560.59492b860e673f1a301981554382934b36589545.nimiux@gentoo \
--to=nimiux@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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