From: Glenn Morris <rgm@gnu.org>
To: bug-gnu-emacs@gnu.org
Subject: bug#953: pre-crt0.o error for build in separate directory
Date: Wed, 10 Sep 2008 00:27:09 -0400 [thread overview]
Message-ID: <5cbpywtyle.fsf@fencepost.gnu.org> (raw)
Package: emacs
Severity: minor
Version: 23.0.60
I don't normally build in a separate directory, but I was trying it as
an experiment.
I had CVS checkout in:
/somedir/trunk
This contained the result of a normal build, ie had not been cleaned.
I then did:
cd /somedir/build
../trunk/configure
which warned me:
WARNING: The directory tree `/somedir/trunk' is being used as a build
directory right now; it has been configured in its own right. To
configure in another directory as well, you MUST use GNU make. If
you do not have GNU make, then you must now do `make distclean' in
/somedir/trunk, and then run ../trunk/configure again."
Since I use GNU make (3.81 on RHEL 5.2), I carried on without running
distclean.
The build failed because /somedir/build/src/pre-crt0.o was not generated.
Running `make prec-crt0.o' in that directory, I was told
that "`/somedir/trunk/src/pre-crt0.o' is up to date."
I had to delete the pre-crt0.o in trunk/src in order to get a version
to compile in build/src.
Thus, the initial message output by configure is incorrect.
I'm not sure where the bug is here: in configure's message, or GNU
make, or Emacs.
(The same thing was happening for character.o and chartab.o until I
fixed their broken dependencies on $(config_h).)
next reply other threads:[~2008-09-10 4:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 4:27 Glenn Morris [this message]
2011-05-20 18:37 ` bug#953: pre-crt0.o error for build in separate directory Glenn Morris
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=5cbpywtyle.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=953@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@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 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.