🚀 go-pugleaf

gcc on OSF systems produces the following link warning, both when building
gcc and occasionally when compiling other programs:

Warning: linking some objects which contain
         exception information and some which do not.  This may
         cause fatal runtime exception handling problems."

Indeed, users on my system complain that when they compile a c++ program
with -fhandle-exceptions, they get a segmentation violation when they try
a throw(), which seems to exactly the problem warned about here. 

What is the difference between the code produced by gcc and that of OSF 
cc, which the linker never complains about?

I know that may OSF gcc users are frustrated by this problem.  How can we
get around it?  (For example, is there a way to force the compiler to
produce object code with exception information?  -fhandle-exceptions
apparently does not do so.)

Thank you,
Karl.