libunwind detection problem

[Josh Parsons]

Hi, all,

I'm working with a crosstool-0.28-rc37 / gcc-3.3.5 toolchain for armv5b-
softfloat and discovered that when the toolchain is built on a build
system with libunwind, the target system is assumed to have libunwind as
well.

The culprit seems to be the libunwind detection code in libstdc++-v3's
configure script, and I have been able to work around the problem by
modifying armv5b-softfloat.dat to add --disable-libunwind-exceptions to
GCC_EXTRA_CONFIG.

This seems as though it shouldn't be necessary, though - gcc shouldn't
be assuming that the target system has libunwind just because the build
system does.

Has anyone else had trouble with this? Should it be regarded as a
crosstool bug, a gcc bug, or neither?

-- 
Josh Parsons
Philosophy Department
1238 Social Sciences and Humanities Bldg.
University of California
Davis, CA 95616-8673
USA
 
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com