Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org
Subject: Re: Updating Autoconf and Automake versions used in GCC and src
Date: Sun, 28 Jun 2009 11:59:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.0906281154000.19992@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20090628072452.GC16677@gmx.de>

On Sun, 28 Jun 2009, Ralf Wildenhues wrote:

> I haven't tried the --with-build-sysroot build; can somebody point out
> to me what I need to do for an effective test of this?  I'm pretty sure
> that updating Autoconf and Automake only will not impact this feature,
> though, but I'll confirm before the switch.

<http://www.eglibc.org/cgi-bin/viewcvs.cgi/*checkout*/trunk/libc/EGLIBC.cross-building?rev=2037> 
describes a procedure for bootstrapping a cross toolchain to a GNU/Linux 
target.  To test with --with-build-sysroot you should install the sysroot 
somewhere other than the configured --with-sysroot value, which then 
requires passing --with-build-sysroot when configuring GCC and 
LDFLAGS_FOR_TARGET and CPPFLAGS_FOR_TARGET (with the appropriate --sysroot 
options) to make when building GCC.

A typical use case would involve a relocatable toolchain and sysroot 
directory: configured --prefix=/some/where 
--with-sysroot=/some/where/sysroot but installed with "make install 
prefix=/other/location".  In this case --with-build-time-tools may also be 
needed when configuring GCC because binutils also will not be in the 
configured location.

-- 
Joseph S. Myers
joseph@codesourcery.com


  reply	other threads:[~2009-06-28 11:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-28  7:25 Ralf Wildenhues
2009-06-28 11:59 ` Joseph S. Myers [this message]
     [not found] <20090628072452.GC16677__5485.08746219358$1246173962$gmane$org@gmx.de>
2009-06-29 17:05 ` Tom Tromey
2009-06-29 18:04   ` Ralf Wildenhues
2009-06-29 18:23     ` Tom Tromey

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=Pine.LNX.4.64.0906281154000.19992@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.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