From: Gaute B Strokkenes <gs234@cam.ac.uk>
Subject: Makefile bug.
Date: 16 May 2001 07:46:57 +0100 [thread overview]
Message-ID: <4ag0e5rdsu.fsf@kern.srcf.societies.cam.ac.uk> (raw)
I'm not sure if this is the right place to report this, but when I did
a make install with CVS gnus as of a few minutes ago, make tried to
create a directory called /emacs and died. If my analysis is correct
this is due to a missing datadir = @datadir@ in gnus/etc/Makefile.in
Additionally, the install target could not deal with a gnus configured
like this:
$ ./configure --prefix=~/elisp/gnus
It worked when I changed it to
$ ./configure --prefix=$HOME/elisp/gnus
I'm not certain if this is supposed to work or not, but I don't see
why it shouldn't. The failure symptoms are mkinstalldirs silently
failing to create the necessary directories.
--
Big Gaute http://www.srcf.ucam.org/~gs234/
I'm having a MID-WEEK CRISIS!
Index: Makefile.in
===================================================================
RCS file: /usr/local/cvsroot/gnus/etc/Makefile.in,v
retrieving revision 1.2
diff -u -p -r1.2 Makefile.in
--- Makefile.in 2000/12/25 05:48:41 1.2
+++ Makefile.in 2001/05/16 06:43:26
@@ -1,3 +1,4 @@
+datadir = @datadir@
infodir = @infodir@
prefix = @prefix@
srcdir = @srcdir@
next reply other threads:[~2001-05-16 6:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-16 6:46 Gaute B Strokkenes [this message]
2001-05-16 9:41 ` Kai Großjohann
2001-05-16 9:51 ` Peter Makholm
2001-05-16 10:09 ` Gaute B Strokkenes
2001-05-16 10:50 ` Kai Großjohann
2001-05-16 12:32 ` Denys Duchier
2001-05-16 13:11 ` Kai Großjohann
2001-05-16 15:18 ` Denys Duchier
2001-05-16 14:20 ` Gaute B Strokkenes
2001-05-16 15:03 ` Kai Großjohann
2001-05-17 0:19 ` Gaute B Strokkenes
2001-05-17 8:45 ` Kai Großjohann
2001-05-16 12:38 ` Michael.Cook
2001-05-16 14:27 ` Karl Kleinpaste
2001-05-16 15:07 ` Kai Großjohann
2001-05-16 16:34 ` Alexandre Oliva
2001-05-17 0:21 ` Gaute B Strokkenes
2001-05-16 18:55 ` Raja R Harinath
2001-05-17 8:45 ` Kai Großjohann
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=4ag0e5rdsu.fsf@kern.srcf.societies.cam.ac.uk \
--to=gs234@cam.ac.uk \
/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).