From: Karl Eichwalder <keichwa@gmx.net>
Subject: Re: Unable to build with /gnu/bin/emacs
Date: Mon, 20 Jan 2003 19:29:17 +0100 [thread overview]
Message-ID: <shu1g3wu82.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: <sh65slynhm.fsf@tux.gnu.franken.de> (Karl Eichwalder's message of "Sun, 19 Jan 2003 19:59:33 +0100")
Karl Eichwalder <keichwa@gmx.net> writes:
> PATH=/gnu/bin:$PATH ./configure --prefix=/gnu \
> --with-url=/usr/share/emacs/site-lisp/url \
> --with-emacs=/gnu/bin/emacs
>
> checking whether make sets $(MAKE)... yes
> checking for a BSD-compatible install... /usr/bin/install -c
> checking for makeinfo... makeinfo
> checking for emacs... /gnu/bin/emacs
> checking if /gnu/bin/emacs is really XEmacs... cat: ./conftest-28855: No such file or directory
Stupid me! I managed to damage my ~/.abbrev_defs file ;-((( After
fixing the the syntax error I was able to compile Gnus as usual.
[Wondering why ./configure resp. 'emacs -q' does care about my
.abbrev_defs file? It seems to read, but not to eval it. Strange.]
--
ke@suse.de (work) / keichwa@gmx.net (home): |
http://www.gnu.franken.de/ke/ | ,__o
Free Translation Project: | _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/ | (*)/'(*)
prev parent reply other threads:[~2003-01-20 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 18:59 Karl Eichwalder
2003-01-20 18:29 ` Karl Eichwalder [this message]
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=shu1g3wu82.fsf@tux.gnu.franken.de \
--to=keichwa@gmx.net \
/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).