public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug objc/44488] objc test inconsistencies w/ / w/out --enable-build-with-cxx
Date: Tue, 11 Jan 2011 09:33:00 -0000 [thread overview]
Message-ID: <bug-44488-4-wdPIWacGjS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-44488-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44488
--- Comment #13 from Iain Sandoe <iains at gcc dot gnu.org> 2011-01-11 08:36:42 UTC ---
(In reply to comment #12)
> (In reply to comment #11)
> > should this be closed as fixed - and, if not, what is the remaining issue?
>
> The remaining issue is that the just built compiler under test looks in
> the install location. I.e. bogus files from a previous borched install could
> cause failures, or a missing file in the build could be masked by having the
> file in the install location.
OK, that is agreed, but AFAIK, it applies to GCC (or the test-suite) as a
whole.
(I'm sure every dev. has at some stage been burnt by a pre-existing install).
It's also an issue when one wants to build version X.Y.Z to sit in the same
place as version P.Q.R.
(--enable-version-specific-runtime-libs is a great option :) ).
Here, I always:
(a) do uninstalled testing
(b) use a different (and unpopulated) install location from the final one when
testing.
(after all, one tends to debug with --enable-checking=yes and build the final
with --enable-checking=release).
---
So, unless I'm missing some finer point of your comment, this is not an
ObjC-specific problem -- perhaps a new PR could be raised for an enhancement to
greater robustness of the test-suite in the presence of installed programs?
next prev parent reply other threads:[~2011-01-11 8:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-44488-4@http.gcc.gnu.org/bugzilla/>
2011-01-10 20:28 ` iains at gcc dot gnu.org
2011-01-10 23:38 ` amylaar at gcc dot gnu.org
2011-01-11 9:33 ` iains at gcc dot gnu.org [this message]
2013-09-14 12:44 ` iains at gcc dot gnu.org
2010-06-10 1:00 [Bug testsuite/44488] New: " amylaar at gcc dot gnu dot org
2010-06-10 1:04 ` [Bug objc/44488] " pinskia at gcc dot gnu dot org
2010-06-10 1:06 ` pinskia at gcc dot gnu dot org
2010-06-10 5:41 ` amylaar at gcc dot gnu dot org
2010-06-10 9:19 ` amylaar at gcc dot gnu dot org
2010-06-10 9:29 ` amylaar at gcc dot gnu dot org
2010-07-09 23:41 ` iains at gcc dot gnu dot org
2010-07-10 10:38 ` iains at gcc dot gnu dot org
2010-07-11 1:01 ` amylaar at gcc dot gnu dot org
2010-07-13 15:20 ` iains at gcc dot gnu dot org
2010-07-13 15:32 ` iains at gcc dot gnu dot org
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=bug-44488-4-wdPIWacGjS@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.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.
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).