public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: What is this check error?
Date: Fri, 16 Apr 2010 15:54:00 -0000	[thread overview]
Message-ID: <4BC85E33.5010906@gmail.com> (raw)
In-Reply-To: <n2o6dc9ffc81004152147g129f398bw5c256fddb0084d0a@mail.gmail.com>

On 16/04/2010 05:47, H.J. Lu wrote:
> On Linux/x86-64, "make check" gave me
> 
> make[6]: *** No rule to make target `check-lto', needed by `check'.
> 
> Where does it come from?

  I saw this too, but now you made me wonder.  So:

  check-lto is in CHECK_TARGETS because all languages are unconditionally
added to check_languages in configure.ac here:

> check_languages=
> for language in $all_selected_languages
> do
> 	check_languages="$check_languages check-$language"
> done

  The check-% targets in Makefile.in are only matched for languages matching
lang_checks:

> # This is only used for check-% targets that aren't parallelized.
> $(filter-out $(lang_checks_parallelized),$(lang_checks)): check-% : site.exp
  [ snip ]

> $(patsubst %,%-subtargets,$(filter-out $(lang_checks_parallelized),$(lang_checks))): check-%-subtargets:

and lang_checks is built up from contributions from each Make-lang.in:

> $ grep lang_checks */Ma*
> cp/Make-lang.in:lang_checks += check-g++
> cp/Make-lang.in:lang_checks_parallelized += check-g++
> fortran/Make-lang.in:lang_checks += check-gfortran
> fortran/Make-lang.in:lang_checks_parallelized += check-gfortran
> objc/Make-lang.in:lang_checks += check-objc
> objcp/Make-lang.in:lang_checks += check-obj-c++

  Probably the simplest solution would be for lto/Make-lang.in to add a dummy
check-lto goal that does nothing, I think.  The original error itself is harmless.

    cheers,
      DaveK

      reply	other threads:[~2010-04-16 12:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-16 11:22 H.J. Lu
2010-04-16 15:54 ` Dave Korn [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=4BC85E33.5010906@gmail.com \
    --to=dave.korn.cygwin@googlemail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    /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.
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).