Re: [PATCH v2] configure: Avoid eh_frame bloat in release builds

Reimar Döffinger <[email protected]>
Newsgroups gmane.comp.video.mplayer.devel
Message-ID <[email protected]>
On Wed, Mar 02, 2016 at 11:27:49PM +0100, Reimar Döffinger wrote:
> 
> 
> On 02.03.2016, at 00:49, Gianluigi Tiesi <[email protected]> wrote:
> 
> > On Sun, Feb 28, 2016 at 02:40:59PM +0100, Reimar Döffinger wrote:
> >> Could you please provide details?
> >> I can't reproduce with neither 32 nor 64 bit mingw64 (latest
> >> Debian version).
> >> I'd rather avoid special cases especially without being
> >> able to include an explanation/reproduction examples.
> > 
> > Hi,
> > 
> > linker error:
> > libmpdemux/demux_rtp.o:demux_rtp.cpp:(.text+0x1985): undefined reference to `__gxx_personality_sj0'
> > libmpdemux/demux_rtp.o:demux_rtp.cpp:(.text+0x19eb): undefined reference to `_Unwind_SjLj_Register'
> > libmpdemux/demux_rtp.o:demux_rtp.cpp:(.text+0x1da2): undefined reference to `_Unwind_SjLj_Unregister'
> > libmpdemux/demux_rtp.o:demux_rtp.cpp:(.text+0x25b2): undefined reference to `_Unwind_SjLj_Resume'
> 
> That explains it, I never tried with the C++ rtp code.
> However the error messages supposedly mean that the gcc version does not support SjLj exceptions.
> However the latest information I have is that that's actually the only exception type supported on 64 bit Windows? It happens for both 32 and 64 bit builds?
> I would prefer to try to understand better, yet as it involves having to have working rtp C++ dependencies it's probably better to remove the option for now.
> Though I wonder if compiling without exception support might be an option, as our code probably doesn't handle exceptions anyway.

While I'd prefer to fix it in a better way, I've for
now disabled that option for MinGW.
_______________________________________________
MPlayer-dev-eng mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/mplayer-dev-eng
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.