From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: Bootstrapping cross-toolchain for ia64
Date: Fri, 04 Nov 2016 12:10:00 -0000 [thread overview]
Message-ID: <64a4cff9-b1d3-4645-7baf-29ec50ebbb94@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1611040044150.20687@digraph.polyomino.org.uk>
On 03/11/2016 22:51, Joseph Myers wrote:
> The current cleanest approach for bootstrapping cross toolchains for
> GNU/Linux targets is (following the guidance at
> <https://sourceware.org/ml/libc-alpha/2012-03/msg00960.html>):
>
> * Build binutils.
>
> * Install kernel headers.
>
> * Build static-only, C-only GCC, configured so that inhibit_libc is
> defined, and using --with-glibc-version so things like stack-smashing
> protection are correctly configured without glibc headers being available.
>
> * Build glibc, which should be identical to what you get from a longer
> sequence of alternating GCC and glibc builds (following fixes I made a few
> years ago for building like that with the initial bootstrap compiler).
>
> * Build GCC with shared libraries and C++ support.
>
> * If you want to run the glibc tests, you should reconfigure / rebuild
> with the new compiler to get everything required for all the tests.
>
> This doesn't work for ia64 because libgcc depends on system headers even
> with inhibit_libc. What's the cleanest approach (assuming recent-enough
> GCC and glibc) for building a cross toolchain for ia64-linux-gnu target,
> so I can make build-many-glibcs.py do whatever's necessary?
I faced the same issue and the solution I found was to configure gcc with
'--disable-shared'. It is not an optimal approach for a complete toolchain,
but it is at least suffice to correctly build glibc.
next prev parent reply other threads:[~2016-11-04 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 0:52 Joseph Myers
2016-11-04 12:10 ` Adhemerval Zanella [this message]
2016-11-04 13:06 ` Joseph Myers
2016-11-04 13:17 ` Adhemerval Zanella
2016-11-04 13:17 ` Dan Horák
2016-11-04 13:31 ` Joseph Myers
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=64a4cff9-b1d3-4645-7baf-29ec50ebbb94@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-alpha@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).