all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Stephen Leake <stephen_leake@stephe-leake.org>
Cc: Fabrice Popineau <fabrice.popineau@gmail.com>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: make check
Date: Wed, 02 Dec 2015 12:07:46 +0000	[thread overview]
Message-ID: <87d1upcaul.fsf@russet.org.uk> (raw)
In-Reply-To: <86bnaau33n.fsf@stephe-leake.org> (Stephen Leake's message of "Mon, 30 Nov 2015 23:53:16 -0600")

Stephen Leake <stephen_leake@stephe-leake.org> writes:

> phillip.lord@russet.org.uk (Phillip Lord) writes:
>
>>> It looks like you are building outside the source tree, as I do; I think
>>> that is broken due to the recent changes in test directory structure.
>>
>> Confused. How do I replicate this?
>
> git clone ... master
>
> cd master
>
> ./autogen.sh
>
> cd ..
>
> mkdir master-build
>
> cd master-build
>
> ../master/configure
>
> make check
>
>
> This allows using the same source tree for different builds with
> different compilers/options. I often maintain a debug and no-debug build
> for the branch I'm working on.


Well, there you go, didn't know that you could do this.

I've just push a commit which (hopefully) fixes this and (hopefully)
doesn't break the more normal build.

Phil



  reply	other threads:[~2015-12-02 12:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-29 22:34 make check Fabrice Popineau
2015-11-30  3:32 ` Eli Zaretskii
2015-11-30 10:52 ` Phillip Lord
2015-11-30 21:00 ` Stephen Leake
2015-11-30 21:06   ` Fabrice Popineau
2015-11-30 22:10   ` Phillip Lord
2015-12-01  5:53     ` Stephen Leake
2015-12-02 12:07       ` Phillip Lord [this message]
2015-12-02 20:27         ` Stephen Leake
2015-12-02 21:09           ` Fabrice Popineau
2015-12-02 21:35             ` Phillip Lord

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=87d1upcaul.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=emacs-devel@gnu.org \
    --cc=fabrice.popineau@gmail.com \
    --cc=stephen_leake@stephe-leake.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.