From: Joseph Myers <joseph@codesourcery.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: <libc-alpha@sourceware.org>
Subject: Re: Bootstrapping cross-toolchain for ia64
Date: Fri, 04 Nov 2016 13:06:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1611041305100.1065@digraph.polyomino.org.uk> (raw)
In-Reply-To: <64a4cff9-b1d3-4645-7baf-29ec50ebbb94@linaro.org>
On Fri, 4 Nov 2016, Adhemerval Zanella wrote:
> 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.
The first GCC (whose build fails) *is* configured with --disable-shared
(and --without-headers --with-newlib to get inhibit_libc defined). It
still tries to build unwind code that includes libc headers
unconditionally.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-11-04 13:06 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
2016-11-04 13:06 ` Joseph Myers [this message]
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=alpine.DEB.2.20.1611041305100.1065@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=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).