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] Bootstrap of combined gcc + binutils, with --enable-shared, with sysroot fails
Date: Thu, 03 Apr 2008 03:25:00 -0000	[thread overview]
Message-ID: <20080403032434.9806.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35804-15855@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from oblivian at users dot sourceforge dot net  2008-04-03 03:24 -------
(In reply to comment #5)
Ok, so this is a sysroot bug in binutils that they marked as invalid
http://sourceware.org/bugzilla/show_bug.cgi?id=4966

I guess I would argue that it's not invalid anymore since this behavior is now
required with the removal of the spec search paths that allowed a minimal
"tools" toolchain to be installed before chrooting and compiling a new full
target toolchain without overwriting binaries.

I applied the change from that bug and now it continues on to stage 2.

This bug is now invalid and it will have to be straightened out with binutils.
My vote is of course this should be supported by sysroot, and not limited to a
root directory chrooted toolchain.


-- 


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


  parent reply	other threads:[~2008-04-03  3:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 16:19 [Bug bootstrap/35804] New: " oblivian at users dot sourceforge dot net
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 [this message]
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=20080403032434.9806.qmail@sourceware.org \
    --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).