public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "oblivian at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/35804]  New: Bootstrap of combined gcc + binutils, with --enable-shared, with sysroot fails
Date: Wed, 02 Apr 2008 16:19:00 -0000	[thread overview]
Message-ID: <bug-35804-15855@http.gcc.gnu.org/bugzilla/> (raw)

Hello,

This bug is a continuation from
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35752 and
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35532. It appears that native
retargeting of the compiler is not supported in the 4.3/4.4 series in favor of
the sysroot option.  When trying to build a pass 1 compiler with combined gcc
and binutils in a single directory, sysroot seems to be appending an extra
sysroot prefix in the linker during libgcc linking.

The current build setup I'm trying is to install in order to the sysroot
directory of /tools:

Linux headers
glibc-pass-1 full compile with native toolchain so that crt files exist.
bootstrap gcc+binutils toolchain against new glibc.

I have tried configuring the gcc+binutils toolchain with the following three
sets of options and it still has the same problem:

configue --prefix=/tools/usr \
         --with-sysroot=/tools \
         --with-pic \
         --disable-nls \
         --disable-libmudflap \
         --disable-libssp \
         --enable-languages=c \
         --enable-checking=release \
         --disable-werror \
         --enable-bootstrap

configue --prefix=/tools/usr \
         --with-sysroot=/tools \
         --with-build-sysroot=/tools \
         --with-pic \
         --disable-nls \
         --disable-libmudflap \
         --disable-libssp \
         --enable-languages=c \
         --enable-checking=release \
         --disable-werror \
         --enable-bootstrap

configue --prefix=/usr \
         --with-sysroot=/tools \
         --with-build-sysroot=/tools \
         --with-pic \
         --disable-nls \
         --disable-libmudflap \
         --disable-libssp \
         --enable-languages=c \
         --enable-checking=release \
         --disable-werror \
         --enable-bootstrap

And building with:
LDFLAGS_FOR_TARGET="--sysroot=/tools" CPPFLAGS_FOR_TARGET="--sysroot=/tools"
make

Everything compiles up to stage 1 libgcc which errors out on the final link
command with the linker error of:
/media/disk-3/build/tools/toolchain-pass-1/build/gcc/../ld/ld-new: cannot find
/tools/lib/libc.so.6 inside /tools

Unfortunately, /tools/lib/libc.so.6 exists and if I create a link to /tools
inside of the tools directory (recursive symlink) the link will complete and
continue to stage 2

I'm pretty sure I shouldn't have to create a link to . for this to work
properly .


-- 
           Summary: Bootstrap of combined gcc + binutils, with --enable-
                    shared, with sysroot fails
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: critical
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: oblivian at users dot sourceforge dot net
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


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


             reply	other threads:[~2008-04-02 16:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 16:19 oblivian at users dot sourceforge dot net [this message]
2008-04-02 16:23 ` [Bug bootstrap/35804] " pinskia at gcc dot gnu dot org
2008-04-02 16:26 ` oblivian at users dot sourceforge dot net
2008-04-02 17:53 ` joseph at codesourcery dot com
2008-04-03  0:12 ` oblivian at users dot sourceforge dot net
2008-04-03  1:41 ` oblivian at users dot sourceforge dot net
2008-04-03  3:25 ` oblivian at users dot sourceforge dot net
2008-04-03 15:08 ` oblivian at users dot sourceforge dot net
2009-01-18 23:36 ` amodra at bigpond dot net dot au
2009-01-19  6:05 ` bonzini at 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-35804-15855@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).