public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Siddhesh Poyarekar <siddhesh@sourceware.org>
Cc: libc-alpha@sourceware.org, joseph@codesourcery.com
Subject: Re: [PATCH] Fix pretty printer tests for run-built-tests == no
Date: Sun, 20 Aug 2017 20:03:00 -0000	[thread overview]
Message-ID: <20170820200349.m7qyt6iohcuvjb6y@aurel32.net> (raw)
In-Reply-To: <1482805594-29119-1-git-send-email-siddhesh@sourceware.org>

On 2016-12-27 07:56, Siddhesh Poyarekar wrote:
> In my change to add configure tests for python I had a brainfart where
> I tried to filter out unsupported tests from tests-printers-programs
> instead of tests-printers to select tests to build.  I realize now
> that all of that is completely unnecessary and it would be safe to
> just build the tests as long as we don't try to run it.

The problem is that the rules to build the tests programs are not
defined if python and python3 are not available. This lead to the
following error when trying to run the tests for a cross compiled
target:

make[3]: *** No rule to make target '/«PKGBUILDDIR»/build-tree/powerpc-ppc64/nptl/test-mutexattr-printers', needed by 'tests'.  Stop

Note those tests are not built for a non-cross compiled target if
python and python3 are not available.

Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

      parent reply	other threads:[~2017-08-20 20:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-27  2:26 Siddhesh Poyarekar
2016-12-28 22:15 ` Adhemerval Zanella
2017-08-20 20:03 ` Aurelien Jarno [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=20170820200349.m7qyt6iohcuvjb6y@aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@sourceware.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.
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).