public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dank at kegel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/12009] New: g++.dg/compat/compat.exp fails to crosscompile testcases
Date: Thu, 21 Aug 2003 13:09:00 -0000	[thread overview]
Message-ID: <20030821130923.12009.dank@kegel.com> (raw)

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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

           Summary: g++.dg/compat/compat.exp fails to crosscompile testcases
           Product: gcc
           Version: 3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dank at kegel dot com
                CC: gcc-bugs at gcc dot gnu dot org

g++.dg/compat/compat.exp sets LD_LIBRARY_PATH properly
for native build/test, but that setting causes compilation
to fail when building/testing a crosscompiler.
The simplest fix is to not touch LD_LIBRARY_PATH et al when
crosscompiling, and let the remote target worry about the runtime
environment.
Please apply
http://www.kegel.com/crosstool/current/gcc-3.4-20030813-patches/compat.exp.patch
Thanks!


             reply	other threads:[~2003-08-21 13:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-21 13:09 dank at kegel dot com [this message]
2003-08-21 13:22 ` [Bug other/12009] g++.dg, compat.exp fail " dank at kegel dot com
2003-08-21 13:33 ` pinskia at gcc dot gnu dot org
2003-08-21 14:24 ` dank at kegel dot com
2003-09-17  5:43 ` pinskia at gcc dot gnu dot org
2003-12-18 19:53 ` cvs-commit at gcc dot gnu dot org
2003-12-18 20:09 ` steven 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=20030821130923.12009.dank@kegel.com \
    --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).