From: Paul Eggert <eggert@cs.ucla.edu>
To: Andreas Schwab <schwab@linux-m68k.org>,
"Herbert J. Skuhra" <hskuhra@eumx.net>,
emacs-devel@gnu.org
Subject: Re: Trunk: Build error on FreeBSD
Date: Sat, 22 Sep 2012 12:00:56 -0700 [thread overview]
Message-ID: <505E0AE8.4090908@cs.ucla.edu> (raw)
In-Reply-To: <85392a6sb4.fsf@iznogoud.viz>
On 09/22/2012 07:32 AM, Wolfgang Jenkner wrote:
> It seems that autoreconf hasn't seen a need
> to update configure, which ends up being older than config.status.
OK, thanks, but in that case, since 'configure' hasn't changed,
why is there a need to touch it? I am guessing that the
touch is to force 'make' to rebuild 'config.status'. But
why bother? If 'configure' hasn't changed, 'config.status'
should not need to be rebuilt.
next prev parent reply other threads:[~2012-09-22 19:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 8:44 Trunk: Build error on FreeBSD Herbert J. Skuhra
2012-09-15 9:33 ` Paul Eggert
2012-09-15 12:48 ` Wolfgang Jenkner
2012-09-17 13:04 ` Wolfgang Jenkner
2012-09-17 21:52 ` Paul Eggert
2012-09-17 22:12 ` Andreas Schwab
2012-09-17 22:37 ` Paul Eggert
2012-09-17 22:42 ` Andreas Schwab
2012-09-17 23:11 ` Paul Eggert
2012-09-18 14:04 ` Wolfgang Jenkner
2012-09-22 7:40 ` Paul Eggert
2012-09-22 10:25 ` Wolfgang Jenkner
2012-09-22 11:04 ` Paul Eggert
2012-09-22 11:17 ` Wolfgang Jenkner
2012-09-22 14:32 ` Wolfgang Jenkner
2012-09-22 19:00 ` Paul Eggert [this message]
2012-09-23 11:42 ` Wolfgang Jenkner
2012-09-23 16:02 ` Paul Eggert
2012-09-23 20:09 ` Wolfgang Jenkner
2012-09-17 22:42 ` Herbert J. Skuhra
2012-09-17 23:23 ` Herbert J. Skuhra
2012-09-18 2:51 ` Stefan Monnier
2012-09-15 20:57 ` Herbert J. Skuhra
2012-09-16 3:42 ` Paul Eggert
2012-09-16 14:39 ` Herbert J. Skuhra
2012-09-16 16:40 ` Paul Eggert
2012-09-17 11:44 ` Herbert J. Skuhra
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=505E0AE8.4090908@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=hskuhra@eumx.net \
--cc=schwab@linux-m68k.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.