This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: __eh_pc undefined is very painful!
- To: mrs at wrs dot com (Mike Stump)
- Subject: Re: __eh_pc undefined is very painful!
- From: "Marty Leisner" <leisner at rochester dot rr dot com>
- Date: Sun, 04 Apr 1999 14:56:00 -0400
- cc: egcs at egcs dot cygnus dot com
I've been using gcc since 1.18.
The last I recall such painfullness was the
difference between 1.x and 2.x (on sparc).
I'm not quite sure what a "major release" is considered.
Is egcs 1.0.3 to egcs 1.1 a major release?
> > To: egcs@egcs.cygnus.com
> > Date: Thu, 01 Apr 1999 00:04:17 -0500
> > From: "Marty Leisner" <leisner@rochester.rr.com>
>
> > (I found the note in the egcs mailing list about this is what
> > happens when you mix old and new compilers).
>
> > But this is so painful!! What does __eh_pc do? Can't you stub it?
> > Or something?
>
> If it is so painful to mix old and new compilers, then maybe you can
> avoid the pain by not trying to mix them? We don't offer much binary
> compatibility between major releases. Please recompile.
>
> Sorry.