public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "developer at sandoe-acoustics dot co dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/43512] [4.5 regression] Many objc test failures
Date: Thu, 25 Mar 2010 20:03:00 -0000	[thread overview]
Message-ID: <20100325200305.17583.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43512-682@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from developer at sandoe-acoustics dot co dot uk  2010-03-25 20:03 -------
(In reply to comment #2)
> Iain, these tests pass if the tests are run after "make install" because then
> the objc header files are found in the install tree.  I tested your patch but
> installed first, that's why I didn't see the failures.

I believe that this is one of those "nasty" side effects of
installed/uninstalled testing..

there are two sets of headers with the same names on a Darwin system - one in
the gcc installation tree - one in /usr/include/objc.

The tests *should* fail on Linux in an ideal world (when -fnext-runtime is
given)  - because they are supposed to be finding the NeXT headers at
/usr/include/objc.  This is a compiler-provided path. 

Of course, once installed the compiler's own headers are found because it
searches through all the various options.. since the header names are the same
.. the fail does not occur.

It's a source of potentially very subtle problems...
(at least, that is my understanding of the situation).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43512


  parent reply	other threads:[~2010-03-25 20:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25  3:01 [Bug testsuite/43512] New: " hjl dot tools at gmail dot com
2010-03-25  3:01 ` [Bug testsuite/43512] " hjl dot tools at gmail dot com
2010-03-25  9:04 ` developer at sandoe-acoustics dot co dot uk
2010-03-25 18:07 ` janis at gcc dot gnu dot org
2010-03-25 20:03 ` developer at sandoe-acoustics dot co dot uk [this message]
2010-03-25 21:40 ` developer at sandoe-acoustics dot co dot uk
2010-03-25 21:42 ` pinskia at gcc dot gnu dot org
2010-03-25 22:26 ` janis at gcc dot gnu dot org
2010-03-26  0:30 ` hjl dot tools at gmail dot com
2010-03-26  7:48 ` developer at sandoe-acoustics dot co dot uk
2010-03-26  8:09 ` developer at sandoe-acoustics dot co dot uk
2010-03-26 13:09 ` hjl dot tools at gmail dot com

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=20100325200305.17583.qmail@sourceware.org \
    --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).