unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: make bootstrap fails.
Date: Sun, 1 Feb 2004 16:08:25 -0600 (CST)	[thread overview]
Message-ID: <200402012208.i11M8OI25458@raven.dms.auburn.edu> (raw)
In-Reply-To: <87n0825vic.fsf@emptyhost.emptydomain.de> (message from Kai Grossjohann on Sun, 01 Feb 2004 22:40:11 +0100)

Kai Grossjohann wrote:

   Before making big changes like this, let's check with the OP whether
   this is really the problem.  Just my two cents.

I do not know whether this is the problem in the case of the OP.  It
is definitely a fact though that if CDPATH is set and does not start
with a colon, problems can develop.

I did:

export CDPATH=~/  (admittedly stupid CDPATH, but still.)
./configure --without-toolkit-scroll-bars
make bootstrap

Result:

[bash2.05b.0 ~/emacscvsdir/emacs 3 11] make bootstrap
(cd src;      make  mostlyclean)
/home/teirllm/src
make[1]: Entering directory `/home/teirllm/src'
make[1]: *** No rule to make target `mostlyclean'.  Stop.
make[1]: Leaving directory `/home/teirllm/src'
make: *** [bootstrap-clean-before] Error 2

The question of whether a change in Makefile.in is necessary is
equivalent to the question of whether the Makefile should support
values of CDPATH not starting with a colon.  (If CDPATH starts with a
colon, there should be no problem.)

Sincerely,

Luc.

  reply	other threads:[~2004-02-01 22:08 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-31  0:02 make bootstrap fails Steven T. Hatton
2004-01-31  0:44 ` Luc Teirlinck
2004-01-31  0:54   ` Steven T. Hatton
2004-01-31  1:32     ` make bootstrap fails. env problem Steven T. Hatton
2004-01-31  0:57   ` make bootstrap fails Steven T. Hatton
2004-01-31  1:48     ` Luc Teirlinck
2004-01-31  2:07       ` Steven T. Hatton
2004-01-31  3:20       ` Steven T. Hatton
2004-02-01 18:10         ` Richard Stallman
2004-01-31 20:02 ` Kai Grossjohann
2004-02-01 21:34   ` Kim F. Storm
2004-02-01 20:52     ` Luc Teirlinck
2004-02-01 21:40       ` Kai Grossjohann
2004-02-01 22:08         ` Luc Teirlinck [this message]
2004-02-02 23:05           ` Richard Stallman
2004-02-03 22:05             ` Luc Teirlinck
2004-02-04 10:07               ` Kim F. Storm
2004-02-04 15:21                 ` Luc Teirlinck
2004-02-04 16:55                   ` Jan D.
2004-02-04 19:36                     ` Luc Teirlinck
2004-02-04 22:51                       ` Kim F. Storm
2004-02-04 20:51                     ` Luc Teirlinck
2004-02-04 16:56                   ` Kim F. Storm
2004-02-01 22:27         ` Luc Teirlinck
2004-02-02  7:09           ` Kai Grossjohann
2004-02-02 14:28             ` Luc Teirlinck
2004-02-02 17:11               ` Stefan Monnier
2004-02-02 18:51                 ` Luc Teirlinck
2004-02-02 20:02                   ` Stefan Monnier
2004-02-02 22:59                     ` Luc Teirlinck
2004-02-02 19:01                 ` Luc Teirlinck
2004-02-01 23:46       ` Kim F. Storm
2004-02-01 23:02         ` Luc Teirlinck
  -- strict thread matches above, loose matches on Subject: below --
2005-07-27 13:35 make (bootstrap) fails Lennart Borgman
2005-07-27 13:47 ` Lennart Borgman
2005-07-27 14:39   ` Juanma Barranquero
2005-07-27 14:50     ` Lennart Borgman
2005-07-27 14:48 ` Eli Zaretskii
2005-07-27 15:13   ` Juanma Barranquero
2003-02-13 23:03 make bootstrap fails Mark Moll
2003-02-14 10:03 ` Juanma Barranquero
2002-11-08 20:04 Kai Großjohann
2002-11-09 13:17 ` Henrik Enberg
2002-11-11 10:19   ` Richard Stallman
2002-11-12 18:29     ` Henrik Enberg
2002-11-14 12:15       ` Richard Stallman
2002-11-14 23:38     ` Kenichi Handa
2002-11-15 14:24       ` Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200402012208.i11M8OI25458@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@gnu.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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).