From: wmperry@aventail.com (William M. Perry)
Cc: Don Croyle <croyle@gelemna.ft-wayne.in.us>, ding@gnus.org
Subject: Re: autoconf support incomplete
Date: 01 Mar 1998 20:07:24 -0800 [thread overview]
Message-ID: <86hg5hloqr.fsf@kramer.in.aventail.com> (raw)
In-Reply-To: François Pinard's message of "01 Mar 1998 22:54:54 -0500"
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 768 bytes --]
François Pinard <pinard@iro.umontreal.ca> writes:
> Don Croyle <croyle@gelemna.ft-wayne.in.us> writes:
>
> > It looks as if the script tests for emacs, but not for xemacs, so I still
> > needed to use an EMACS=xemacs argument for the make.
>
> Unless I'm mistaken, the script should test for `xemacs' *if* `emacs' is
> not found, so `EMACS=xemacs' should not be required on `make' when
> `xemacs' is the only available Emacs. It this does not work, I would be
> curious to know why it does not. On the other hand, if it works, I also
> hope someone will tell us.
There is nothing in the configure.in file that would cause this
behaviour. I'm going to start working right now on an improved
configure.in for Gnus. I'll have it done in a few hours.
-Bill P.
next prev parent reply other threads:[~1998-03-02 4:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-01 22:13 Don Croyle
1998-03-01 22:17 ` Stefan Waldherr
1998-03-07 12:44 ` Lars Magne Ingebrigtsen
1998-03-07 14:05 ` Stefan Waldherr
1998-03-07 14:40 ` Lars Magne Ingebrigtsen
[not found] ` <6dcnq3$nti$1@catastrophe.gelemna.ft-wayne.in.us>
1998-03-01 22:56 ` Don Croyle
1998-03-01 23:52 ` William M. Perry
[not found] ` <6dcson$qog$1@catastrophe.gelemna.ft-wayne.in.us>
1998-03-02 0:52 ` Don Croyle
1998-03-02 3:54 ` François Pinard
1998-03-02 4:07 ` William M. Perry [this message]
1998-03-02 4:21 ` William M. Perry
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=86hg5hloqr.fsf@kramer.in.aventail.com \
--to=wmperry@aventail.com \
--cc=croyle@gelemna.ft-wayne.in.us \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).