This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug objc/44488] objc test inconsistencies w/ / w/out --enable-build-with-cxx
- From: "amylaar at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 10 Jan 2011 23:18:17 +0000
- Subject: [Bug objc/44488] objc test inconsistencies w/ / w/out --enable-build-with-cxx
- Auto-submitted: auto-generated
- References: <bug-44488-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44488
--- Comment #12 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> 2011-01-10 23:18:09 UTC ---
(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.
There are ways to manage this issue, like always picking a new, un-populated
install location for test builds. That's what I usually do now, so this
problem affects me no longer.
OTOH, if such a test methodology is generally used, we run the risk that
building with a populated install location will bitrot.