From: Brian Gough <bjg@network-theory.co.uk>
To: gsl-discuss@sourceware.org
Subject: Re: Suggestion: Exception Support
Date: Mon, 17 Dec 2007 17:27:00 -0000 [thread overview]
Message-ID: <874pehz0yz.wl%bjg@network-theory.co.uk> (raw)
In-Reply-To: <7ECEBD13-EFAD-4117-AC8D-E4929B455767@comhem.se>
At Mon, 17 Dec 2007 15:17:22 +0100,
Tommy Nordgren wrote:
> I suggest that the configure script should be set up so that make
> will build the GSL library with C++ exception support if
> possible. (C code must be compiled with the flag -fexceptions under
> gcc) I've noticed that configure don't turn on this flag by default.
> (If a c library is NOT compiled with -fexecptions, any exception
> thrown across a c function call on the stack, will always terminate
> the application)
Thanks for the suggestion. It probably would be more convenient, but
changing the autoconf defaults tends to cause unexpected problems so I
prefer to stick with them.
I'll add a note in the INSTALL file to make the -fexceptions option
more prominent. Presumably most distributions should be adding this
anyway.
--
Brian Gough
prev parent reply other threads:[~2007-12-17 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 14:17 Tommy Nordgren
2007-12-17 17:27 ` Brian Gough [this message]
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=874pehz0yz.wl%bjg@network-theory.co.uk \
--to=bjg@network-theory.co.uk \
--cc=gsl-discuss@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).