From: "H. J. Lu" <hjl@lucon.org>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sources.redhat.com
Subject: Re: PATCH: Test the just built windres/dlltool only
Date: Mon, 21 Feb 2005 21:09:00 -0000 [thread overview]
Message-ID: <20050221174324.GA1042@lucon.org> (raw)
In-Reply-To: <421A1E0B.4080306@redhat.com>
On Mon, Feb 21, 2005 at 05:44:43PM +0000, Nick Clifton wrote:
> Hi H. J.
>
> >>>windres/dlltool may not be built for all platforms. But we are picking
> >>>up them from PATH even if they weren't built at all. This patch
> >>>changes it.
> >>
> >>If they are on your $PATH, why aren't we building them? This patch
>
> >It is configured for a different target.
>
> >>will disable the tests when testing an installed binutils, I think.
>
> >How do you test the installed binutils with the binutils build tree?
> >I thought you should set them in environment if you wanted to test the
> >installed ones.
>
> I think that the point is that you should set the PATH in your
> environment to only include the built tools for your current target, not
> for other targets. Otherwise you could end up testing the entirely
> wrong set of tools.
>
My PATH has binaries for my host machine, which are irrelevant to the
target for my binutils built tree. I don't think
# configure
# make
# make check
should test any of my install binaries. "make check" should assume
my installed binaries are OK. I still haven't seen a reasonable reason
for "make check" to test the installed binaries.
H.J.
next prev parent reply other threads:[~2005-02-21 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 8:37 H. J. Lu
2005-02-21 9:59 ` Daniel Jacobowitz
2005-02-21 10:29 ` H. J. Lu
2005-02-21 20:38 ` Nick Clifton
2005-02-21 21:09 ` H. J. Lu [this message]
2005-02-22 19:23 ` Nick Clifton
2005-02-23 2:26 ` H. J. Lu
2005-02-23 16:11 ` Nick Clifton
2005-02-24 5:37 ` H. J. Lu
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=20050221174324.GA1042@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--cc=nickc@redhat.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).