From: Lloyd Zusman <ljz@asfast.com>
Subject: [PATCH] Non-standard lispdir
Date: 05 Dec 1998 07:45:55 -0500 [thread overview]
Message-ID: <ltpv9yrc3g.fsf@asfast.com> (raw)
In-Reply-To: Graham Murray's message of "05 Dec 1998 06:02:11 +0000"
I'm using pgnus-0.63.
I like to store the Gnus *.elc files in a non-standard area, and so
I have patched the `configure' script to allow a `--lispdir' parameter.
This lets us explicitly set the `lispdir' variable in the Makefiles
to a value of our choice.
Would it be possible to make this part of the offical Gnus `configure'
script?
Lloyd Zusman
ljz@asfast.com
---------------------------------- cut here ----------------------------------
*** configure.orig Sat Dec 5 07:20:48 1998
--- configure Sat Dec 5 07:37:31 1998
***************
*** 45,50 ****
--- 45,51 ----
oldincludedir='/usr/include'
infodir='${prefix}/info'
mandir='${prefix}/man'
+ lispdir=NONE
# Initialize some other variables.
subdirs=
***************
*** 157,162 ****
--- 158,164 ----
[PREFIX/com]
--localstatedir=DIR modifiable single-machine data in DIR [PREFIX/var]
--libdir=DIR object code libraries in DIR [EPREFIX/lib]
+ --lispdir=DIR lisp code in DIR [PREFIX/lisp]
--includedir=DIR C header files in DIR [PREFIX/include]
--oldincludedir=DIR C header files for non-gcc in DIR [/usr/include]
--infodir=DIR info documentation in DIR [PREFIX/info]
***************
*** 214,219 ****
--- 216,226 ----
| --libexe=* | --libex=* | --libe=*)
libexecdir="$ac_optarg" ;;
+ -lispdir | --lispdir | --lispdi | --lispd | --lisp)
+ ac_prev=lispdir ;;
+ -lispdir=* | --lispdir=* | --lispdi=* | --lispd=* | --lisp=*)
+ lispdir="$ac_optarg" ;;
+
-localstatedir | --localstatedir | --localstatedi | --localstated \
| --localstate | --localstat | --localsta | --localst \
| --locals | --local | --loca | --loc | --lo)
***************
*** 659,667 ****
echo "$ac_t""no" 1>&6
fi
if test $EMACS != "no"; then
echo $ac_n "checking where .elc files should go""... $ac_c" 1>&6
! echo "configure:665: checking where .elc files should go" >&5
lispdir="\$(datadir)/emacs/site-lisp"
if test "x$prefix" = "xNONE"; then
if test -d $ac_default_prefix/share/emacs/site-lisp; then
--- 666,675 ----
echo "$ac_t""no" 1>&6
fi
+ if test "x$lispdir" = "xNONE"; then
if test $EMACS != "no"; then
echo $ac_n "checking where .elc files should go""... $ac_c" 1>&6
! echo "configure:672: checking where .elc files should go" >&5
lispdir="\$(datadir)/emacs/site-lisp"
if test "x$prefix" = "xNONE"; then
if test -d $ac_default_prefix/share/emacs/site-lisp; then
***************
*** 677,692 ****
else
if test -d $prefix/lib/emacs/site-lisp; then
lispdir="\$(prefix)/lib/emacs/site-lisp"
! fi
fi
fi
- echo "$ac_t""$lispdir" 1>&6
fi
# Extract the first word of "makeinfo", so it can be a program name with args.
set dummy makeinfo; ac_word=$2
echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:690: checking for $ac_word" >&5
if eval "test \"`echo '$''{'ac_cv_path_MAKEINFO'+set}'`\" = set"; then
echo $ac_n "(cached) $ac_c" 1>&6
else
--- 685,701 ----
else
if test -d $prefix/lib/emacs/site-lisp; then
lispdir="\$(prefix)/lib/emacs/site-lisp"
! fi
fi
fi
fi
+ echo "$ac_t""$lispdir" 1>&6
+ fi
# Extract the first word of "makeinfo", so it can be a program name with args.
set dummy makeinfo; ac_word=$2
echo $ac_n "checking for $ac_word""... $ac_c" 1>&6
! echo "configure:697: checking for $ac_word" >&5
if eval "test \"`echo '$''{'ac_cv_path_MAKEINFO'+set}'`\" = set"; then
echo $ac_n "(cached) $ac_c" 1>&6
else
next reply other threads:[~1998-12-05 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-05 12:45 Lloyd Zusman [this message]
1998-12-05 13:42 ` Karl Eichwalder
1998-12-10 4:20 ` Lloyd Zusman
1998-12-10 21:09 ` Karl Eichwalder
1998-12-11 8:47 ` Stephen Zander
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=ltpv9yrc3g.fsf@asfast.com \
--to=ljz@asfast.com \
/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).