http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52990
Thierry Reding <thierry.red...@avionic-design.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |thierry.reding@avionic-desi
| |gn.de
--- Comment #1 from Thierry Reding <thierry.red...@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.
