public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/54283] New: [4.8 regression] build tools don't run after cxx-conversion merge
Date: Thu, 16 Aug 2012 13:45:00 -0000	[thread overview]
Message-ID: <bug-54283-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 54283
           Summary: [4.8 regression] build tools don't run after
                    cxx-conversion merge
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: ro@gcc.gnu.org
                CC: crowl@gcc.gnu.org, dnovillo@gcc.gnu.org
              Host: *-*-solaris2.*
            Target: *-*-solaris2.*
             Build: *-*-solaris2.*


Since the merge of the cxx-conversion branch, Solaris bootstrap fails for me.
In stage 1, the build tools fail to run, e.g.

build/genmddeps /vol/gcc/src/hg/trunk/local/gcc/config/i386/i386.md >
tmp-mddeps
ld.so.1: genmddeps: fatal: libstdc++.so.6: open failed: No such file or
directory
make[3]: *** [s-mddeps] Killed
make[3]: *** Waiting for unfinished jobs....

I'm using a self-built gcc 4.4.2 as bootstrap compiler, installed into
/vol/gcc-4.4.  In order to assure that the libstdc++.so.6 included there is
found,
I've so far been configuring with

--with-host-libstdcxx=\'-L/vol/gcc-4.4/lib -Wl,-Bstatic -lstdc++ -Wl,-Bdynamic
-lm\' --with-boot-ldflags=\'-static-libstdc++' -static-libgcc
-L/vol/gcc-4.4/lib\'

This is not enough after the conversion since the build tools don't use either
$BOOT_LDFLAGS or $HOST_LIBS.

The attached patch allowed the bootstrap to finish, but is obviously wrong
as-is
since it doesn't correctly distinguish between build and host tools.  Having
never run a canadian cross myself, I'm not sure what the right approach is.

The first part (using $CC as linker instead of $CXX_FOR_BUILD) is necessary to
avoid linking with g++ which links with -lstdc++ on its own.

  Rainer


             reply	other threads:[~2012-08-16 13:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16 13:45 ro at gcc dot gnu.org [this message]
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
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@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).