From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: [PATCH] Non-standard lispdir
Date: 09 Dec 1998 23:20:12 -0500 [thread overview]
Message-ID: <ltogpcy6f7.fsf@asfast.com> (raw)
In-Reply-To: Karl Eichwalder's message of "05 Dec 1998 14:42:45 +0100"
Karl Eichwalder <ke@gnu.franken.de> writes:
> Lloyd Zusman <ljz@asfast.com> writes:
>
> | 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.
>
> It's a good idea to make `lispdir' available to the `configure' script;
> but the right approach would be to patch `configure.in' to let
> `autoconf' do the dirty work. Have a look how the `w3' package tries to
> solve the problem
> [ ... ]
Thanks ... I very much appreciate this information. :)
> AC_EMACS_PACKAGES
> AC_PATH_LISPDIR
> AC_EMACS_VERSION
>
> I'm not sure whether these are the "official" ones -- they are working
> pretty well. I'll check it the next week.
Well, it looks like I'd have make use of a customized AC_INIT macro in order
to add a --lispdir argument to the Gnus `configure.in' script ... or am
I missing something? Any ideas?
> | This lets us explicitly set the `lispdir' variable in the Makefiles
> | to a value of our choice.
>
> That's already working; simply call `make' this way:
>
> make lispdir=/usr/share/emacs/site-lisp/gnus
> make lispdir=/usr/share/emacs/site-lisp/gnus install
Yes ... I know I can do this, but I was hoping to make this part of
`configure' so I only have to type the lisp directory once (during
initial configuration), and then call `make' as follows:
make
make install
--
Lloyd Zusman
ljz@asfast.com
next prev parent reply other threads:[~1998-12-10 4:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-05 12:45 Lloyd Zusman
1998-12-05 13:42 ` Karl Eichwalder
1998-12-10 4:20 ` Lloyd Zusman [this message]
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=ltogpcy6f7.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).