public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/30675]  New: [4.2/4.3 Regression] libstdc++ testsuite hardcodes "ar" and "ranlib"
Date: Fri, 02 Feb 2007 02:30:00 -0000	[thread overview]
Message-ID: <bug-30675-230@http.gcc.gnu.org/bugzilla/> (raw)

libstdc++-v3/testsuite/lib/libstdc++.exp contains code:

    # Collect into libtestc++.a
    set arcommand "ar -rc ./libtestc++.a ${libtest_objs}"
    set result [lindex [local_exec "$arcommand" "" "" 300] 0]
    verbose "link result is $result"
    if { $result == 0 } {
        set ranlibcommand "ranlib ./libtestc++.a"
        set result [lindex [local_exec "$ranlibcommand" "" "" 300] 0]
        if { $result != 0 } {
            error "could not link libtestc++.a"
        }
    }

For a cross-compiler this should use $target-ar and $target-ranlib, not plain
"ar" and "ranlib".


-- 
           Summary: [4.2/4.3 Regression] libstdc++ testsuite hardcodes "ar"
                    and "ranlib"
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jsm28 at gcc dot gnu dot org


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


             reply	other threads:[~2007-02-02  2:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-02  2:30 jsm28 at gcc dot gnu dot org [this message]
2007-02-02 11:32 ` [Bug libstdc++/30675] " bkoz at gcc dot gnu dot org
2007-02-03 17:32 ` jsm28 at gcc dot gnu dot org
2007-02-19 21:03 ` mmitchel at gcc dot gnu dot org
2007-03-05 13:41 ` jsm28 at gcc dot gnu dot org
2007-03-05 22:07 ` jsm28 at gcc dot gnu dot org
2007-03-05 22:08 ` jsm28 at gcc dot gnu dot org
2007-03-08 11:50 ` jsm28 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=bug-30675-230@http.gcc.gnu.org/bugzilla/ \
    --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).