This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/12276] [3.3/3.4 regression] Configure check for libunwind does not work with cross
- From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 2 Oct 2003 22:12:43 -0000
- Subject: [Bug bootstrap/12276] [3.3/3.4 regression] Configure check for libunwind does not work with cross
- References: <20030914163803.12276.schwab@suse.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12276
mmitchel at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From mmitchel at gcc dot gnu dot org 2003-10-02 22:12 -------
Apparently, this was considered to be desirable behavior; the ChangeLog says:
2002-10-02 David Mosberger-Tang <David.Mosberger@acm.org>
* configure.in: Move sjlj-exceptions and --enable-libunwind-exceptions
before inclusion of config.gcc, but after configuring the compiler etc.
Determine default value for --enable-libunwind-exceptions based on
whether the host has a libunwind library (not guaranteed to be correct,
but it's a reasonable first guess and can always be overridden with an
explicit --enable/disable-libunwind-exceptions.
Therefore, I've closed this bug. If you still think it's a bug, bring it up on
the GCC mailing list and see if you can get consensus about that.