public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: hjl@lucon.org (H.J. Lu)
To: egcs@cygnus.com
Subject: A patch for dejagnu
Date: Wed, 11 Mar 1998 09:39:00 -0000	[thread overview]
Message-ID: <m0yCpT3-00058JC@ocean.lucon.org> (raw)

Hi,

Some people have reported problems with the latest dejagnu and
egcs that dejagnu cannot find the correct libstdc++ and libio.
Here is a patch which seems to work for me.


-- 
H.J. Lu (hjl@gnu.org)
---
--- libgloss.exp.orig	Wed Mar 11 08:26:07 1998
+++ libgloss.exp	Wed Mar 11 09:33:34 1998
@@ -425,14 +425,17 @@
 
 
     # search for the top level multilib directory
-    set multitop [lookfor_file "${comp_base_dir}" "${target_alias}"]
+    set multitop [lookfor_file "${comp_base_dir}" "libraries"]
     if { $multitop == "" } {
-	set multitop [lookfor_file "${comp_base_dir}" "libraries"]
-	if { $multitop == "" } {
-	    set multitop "[lookfor_file ${comp_base_dir} gcc/xgcc]"
-	    if { $multitop != "" } {
-		set multitop [file dirname [file dirname $multitop]];
-	    } else {
+	set multitop "[lookfor_file ${comp_base_dir} gcc/xgcc]"
+	if { $multitop != "" } {
+	    set multitop [file dirname [file dirname $multitop]];
+	} else {
+	    # We search ${target_alias} last since it is only valid
+	    # when we are running dejagnu on an installed gcc. We
+	    # don't want to get it by accident.
+	    set multitop [lookfor_file "${comp_base_dir}" "${target_alias}"]
+	    if { $multitop == "" } {
 		return ""
 	    }
 	}

             reply	other threads:[~1998-03-11  9:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-11  9:39 H.J. Lu [this message]
1998-03-12 17:00 ` Jim Wilson
1998-03-16 20:04   ` Jeffrey A Law
1998-05-28  6:19 none Jeffrey A Law
1998-05-28 17:47 ` A patch for dejagnu H.J. Lu

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=m0yCpT3-00058JC@ocean.lucon.org \
    --to=hjl@lucon.org \
    --cc=egcs@cygnus.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).