unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: David Kastrup <dak@gnu.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: More fun with vcswitness
Date: Sun, 12 Jan 2014 23:19:42 +0100	[thread overview]
Message-ID: <AB0D3F1A-9F56-47A3-A135-E7F089E5133B@swipnet.se> (raw)
In-Reply-To: <83k3e47vlq.fsf@gnu.org>

Hello.

12 jan 2014 kl. 22:12 skrev Eli Zaretskii <eliz@gnu.org>:

> srcdir should always be a relative file name, like ../foo, never
> absolute.

Is this the srcdir used when compiling in a separate directory?
Then there is a problem.  See bug 15795 (http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15795#11) where this was said:

4 nov 2013 kl. 09:10 skrev Glenn Morris <rgm@gnu.org>:

> 
> PS try configuring your out-of-tree build using an absolute path to the
> srcdir.

So srcdir is recommended to be absolute in this case.  Not that I've seen anywhere stating that separate build directory should use relative paths.
Of course if compile mode was smarter this could go away.

Ignore if you are talking about another srcdir.

	Jan D.




  parent reply	other threads:[~2014-01-12 22:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-12 20:07 Mopre fun with vcswitness Eric S. Raymond
2014-01-12 20:14 ` Andreas Schwab
2014-01-12 21:08   ` Eli Zaretskii
2014-01-12 20:18 ` David Kastrup
2014-01-12 20:31   ` Eric S. Raymond
2014-01-12 20:46     ` David Kastrup
2014-01-12 21:02       ` Eric S. Raymond
2014-01-12 21:12   ` Eli Zaretskii
2014-01-12 21:30     ` David Kastrup
2014-01-12 22:19     ` Jan Djärv [this message]
2014-01-13  2:46       ` More " Glenn Morris
2014-01-13  3:50         ` Eli Zaretskii
2014-01-13  4:19           ` Stefan Monnier
2014-01-13 10:12             ` Andreas Schwab
2014-01-13 11:12               ` David Kastrup
2014-01-13 11:30                 ` Andreas Schwab
2014-01-13 14:30               ` Stefan Monnier
2014-01-13 17:37                 ` Glenn Morris
2014-01-13 19:03           ` Glenn Morris
2014-01-13 19:13             ` Eli Zaretskii

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=AB0D3F1A-9F56-47A3-A135-E7F089E5133B@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=dak@gnu.org \
    --cc=eliz@gnu.org \
    --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).