From: Chris Marusich <cmmarusich@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: Is it necessary to run "make" before "make check"?
Date: Sun, 17 Dec 2017 18:26:15 -0800 [thread overview]
Message-ID: <8760946abc.fsf@gmail.com> (raw)
In-Reply-To: <20171217151213.47ccd4a3@scratchpost.org> (Danny Milosavljevic's message of "Sun, 17 Dec 2017 15:12:13 +0100")
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
Danny Milosavljevic <dannym@scratchpost.org> writes:
> On Sun, 17 Dec 2017 14:26:30 +0100
> Danny Milosavljevic <dannym@scratchpost.org> wrote:
>
>> Hi,
>>
>> On Thu, 07 Dec 2017 18:17:49 -0800
>> Chris Marusich <cmmarusich@gmail.com> wrote:
>>
>> > Is it necessary to run "make" before "make check",
>>
>> No.
>>
>> >or is it good enough
>> > to just run "make check" and rely on Make to build whatever needs to be
>> > built to run "make check"?
>>
>> Yes.
>>
>> See the Makefile:
>>
>> all: $(BUILT_SOURCES)
>> check: $(BUILT_SOURCES)
>
> And also
>
> check-am: all-am
> all-am: ...
>
> And also a Rube-Goldberg-esque contraption for all-recursive, check-recursive which invokes "make" inside SUBDIRS. *shakes head*
Thank you for pointing to the relevant lines in the Makefile!
> Interesting :)
That's one way to put it... :-)
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-12-18 2:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 2:17 Is it necessary to run "make" before "make check"? Chris Marusich
2017-12-10 16:29 ` Catonano
2017-12-17 13:26 ` Danny Milosavljevic
2017-12-17 14:12 ` Danny Milosavljevic
2017-12-18 2:26 ` Chris Marusich [this message]
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=8760946abc.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=dannym@scratchpost.org \
--cc=guix-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 external index
https://git.savannah.gnu.org/cgit/guix.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.