public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "thierry.reding@avionic-design.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52990] bootstrap ia64 cross-compiler gcc (static C-only) includes a broken libgcc.a due to libunwind dependencies
Date: Fri, 24 Aug 2012 08:43:00 -0000 [thread overview]
Message-ID: <bug-52990-4-LobX3dXrrj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52990-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52990
Thierry Reding <thierry.reding@avionic-design.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |thierry.reding@avionic-desi
| |gn.de
--- Comment #1 from Thierry Reding <thierry.reding@avionic-design.de> 2012-08-24 08:43:16 UTC ---
I've seen this problem when building glibc as well. It tries to build
a number of utilities and link them against libgcc with the missing
symbols that you mentioned.
In the scripts that I use to build the toolchains, I was able to solve
this by adding a configparms file to the build directory that sets
"build-programs = no".
After the final gcc is built, libunwind is properly installed and can
at least be used for dynamically linked executables. I've also tested
that the resulting gcc can link static executables, though I'm not
able to execute because I lack the hardware.
next prev parent reply other threads:[~2012-08-24 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-14 22:32 [Bug target/52990] New: " vapier at gentoo dot org
2012-08-24 8:43 ` thierry.reding@avionic-design.de [this message]
2012-08-24 15:41 ` [Bug target/52990] " vapier at gentoo 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-52990-4-LobX3dXrrj@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).