From: Don Croyle <croyle@gelemna.ft-wayne.in.us>
Subject: Re: autoconf support incomplete
Date: 01 Mar 1998 19:52:54 -0500 [thread overview]
Message-ID: <86g1l1ewwp.fsf@emerson.gelemna.ft-wayne.in.us> (raw)
In-Reply-To: <6dcson$qog$1@catastrophe.gelemna.ft-wayne.in.us>
wmperry@aventail.com (William M. Perry) writes:
> slap this install-sh in the qgnus directory. Lars - glad to see autoconf
> in GNUS! Haven't had time to follow the dev discussion lately. I'm
> downloading the latest qgnus and will probably do a little bit of hacking
> on it before I leave work.
Ok, that gets configure working and it builds. 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. A make install (which looks
like it should adjust some permissions and install the info files in
/usr/local/info) fails for want of mkinstalldirs:
em:/usr/local/lib/xemacs/qgnus#make EMACS=xemacs install
cd lisp && make EMACS=xemacs install
xemacs -batch -q -no-site-file -l ./dgnushack.el -f dgnushack-compile
Loading ./lpath.el...
/bin/sh ../mkinstalldirs
../mkinstalldirs: Can't open ../mkinstalldirs
*** Error code 2
Stop.
*** Error code 1
Stop.
em:/usr/local/lib/xemacs/qgnus#
--
I've always wanted to be a dilettante, but I've never quite been ready
to make the commitment.
next prev parent reply other threads:[~1998-03-02 0:52 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 [this message]
1998-03-02 3:54 ` François Pinard
1998-03-02 4:07 ` William M. Perry
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=86g1l1ewwp.fsf@emerson.gelemna.ft-wayne.in.us \
--to=croyle@gelemna.ft-wayne.in.us \
/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).