From: DJ Delorie <dj@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: janis187@us.ibm.com, gcc-patches@gcc.gnu.org
Subject: Re: [patch, testsuite] set GCC_EXEC_PREFIX *before* building testglue.c
Date: Wed, 19 Aug 2009 08:47:00 -0000 [thread overview]
Message-ID: <200908190141.n7J1f4xd020730@greed.delorie.com> (raw)
In-Reply-To: <6dc9ffc80908181815i4a468541i3d32d8fd4ddf8f0@mail.gmail.com> (hjl.tools@gmail.com)
> http://gcc.gnu.org/ml/gcc-testresults/2009-08/msg01955.html
>
> there are no libstdc++ test results at all and libffi tests never run.
Ah, found it. Everything else that uses wrapper.exp gives a full
path, but loads target-libpath.exp manually. So I did the same for
gcc. I'm checking in this change, please let me know if your test
results go back to normal.
* lib/wrapper.exp: Move load of target-libpath.exp from here...
* lib/gcc-defs.exp: ... to here.
Index: lib/wrapper.exp
===================================================================
--- lib/wrapper.exp (revision 150928)
+++ lib/wrapper.exp (working copy)
@@ -13,14 +13,12 @@
# You should have received a copy of the GNU General Public License
# along with GCC; see the file COPYING3. If not see
# <http://www.gnu.org/licenses/>.
# This file contains GCC-specifics for status wrappers for test programs.
-load_lib target-libpath.exp
-
# ${tool}_maybe_build_wrapper -- Build wrapper object if the target
# needs it. FILENAME is the path to the wrapper file. If there are
# additional arguments, they are command-line options to provide to
# the compiler when compiling FILENAME.
proc ${tool}_maybe_build_wrapper { filename args } {
Index: lib/gcc-defs.exp
===================================================================
--- lib/gcc-defs.exp (revision 150928)
+++ lib/gcc-defs.exp (working copy)
@@ -11,12 +11,14 @@
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with GCC; see the file COPYING3. If not see
# <http://www.gnu.org/licenses/>.
+load_lib target-libpath.exp
+
load_lib wrapper.exp
#
# ${tool}_check_compile -- Reports and returns pass/fail for a compilation
#
prev parent reply other threads:[~2009-08-19 1:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 18:57 DJ Delorie
2009-08-18 19:01 ` Janis Johnson
2009-08-18 19:14 ` DJ Delorie
2009-08-19 3:18 ` H.J. Lu
2009-08-19 8:15 ` DJ Delorie
2009-08-19 8:25 ` H.J. Lu
2009-08-19 8:47 ` DJ Delorie [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=200908190141.n7J1f4xd020730@greed.delorie.com \
--to=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=janis187@us.ibm.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).