public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/54283] [4.8 regression] build tools don't run after cxx-conversion merge
Date: Tue, 18 Dec 2012 12:06:00 -0000	[thread overview]
Message-ID: <bug-54283-4-i9EKYilVcR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54283-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #10 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2012-12-18 12:06:21 UTC ---
> --- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-12-18 10:30:12 UTC ---
> So not a bug then?

I don't think so: even on x86_64-unknown-linux-gnu, when building an
i686-unknown-linux-gnu compiler with an unbundled gcc 4.4 (which does
support -static-libstdc++) where the 32-bit libstdc++.so.6 doesn't live
in /usr/lib, but only in /vol/gcc-4.4/lib, the build tools are the only
ones that don't run.  If it were host and build tools alike, I'd agree,
but the host tools are fine, as they were before the cxx-conversion.

    Rainer


  parent reply	other threads:[~2012-12-18 12:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16 13:45 [Bug bootstrap/54283] New: " ro at gcc dot gnu.org
2012-08-16 13:53 ` [Bug bootstrap/54283] " ro at gcc dot gnu.org
2012-08-16 13:55 ` ro at gcc dot gnu.org
2012-08-16 15:29 ` rguenth at gcc dot gnu.org
2012-09-19 14:33 ` rguenth at gcc dot gnu.org
2012-11-16  1:06 ` pinskia at gcc dot gnu.org
2012-11-16  9:11 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-11-17 10:20 ` ebotcazou at gcc dot gnu.org
2012-11-17 23:31 ` ebotcazou at gcc dot gnu.org
2012-11-28 19:21 ` aoliva at gcc dot gnu.org
2012-11-28 21:41 ` ebotcazou at gcc dot gnu.org
2012-12-18 10:30 ` jakub at gcc dot gnu.org
2012-12-18 12:06 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2012-12-18 12:10 ` jakub at gcc dot gnu.org
2012-12-18 12:13 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-12-19 11:59 ` ebotcazou at gcc dot gnu.org
2012-12-19 12:04 ` jakub at gcc dot gnu.org
2012-12-19 14:34 ` ro at CeBiTec dot Uni-Bielefeld.DE
2013-01-07 12:09 ` ro at CeBiTec dot Uni-Bielefeld.DE
2013-01-07 12:56 ` jakub at gcc dot gnu.org
2013-01-07 13:02 ` jakub at gcc dot gnu.org
2013-01-07 13:06 ` ro at CeBiTec dot Uni-Bielefeld.DE

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-54283-4-i9EKYilVcR@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).