The patch below on the gcc-patches ML allows bootstrapping to go
through for mingw i686 dwarf2-eh builds:

https://gcc.gnu.org/ml/gcc-patches/2015-05/msg01212.html

It could probably use someone else's eyes on it.

On Mon, May 11, 2015 at 9:28 AM, Matt Breedlove
<breedlove.m...@gmail.com> wrote:
> I assumed as much.  I spent a decent amount of time trying to diagnose
> the issue and test with different configs as well as searched across
> google before raising the issue but the only thing I could find was a
> pastebin from someone running into the same issue but no references to
> the link it was posted under.  Has anyone reported this?  I haven't
> seen anything in gcc's bugtraq that looks relevant.
>
> On Mon, May 11, 2015 at 8:16 AM, David Macek <david.mace...@gmail.com> wrote:
>> On 11. 5. 2015 13:52, Matt Breedlove wrote:
>>> Also, I'm experiencing a currently unresolved issue building gcc
>>> 5.1/5.1.1 natively for i686 using dw2 exceptions resulting in it
>>> failing out with the following during stage1 libgcc:
>>>
>>> M:\\msys64\\build\\staging\\mingw-w64-i686-gcc5\\src\\build-i686-w64-mingw32\\i686-w64-mingw32\\libgcc/../../../gcc-5.1.1/libgcc/libgcc2.c:2240:
>>> undefined reference to `__EH_FRAME_BEGIN__'
>>> __main_s.o: In function `_do_global_ctors':
>>> M:\\msys64\\build\\staging\\mingw-w64-i686-gcc5\\src\\build-i686-w64-mingw32\\i686-w64-mingw32\\libgcc/../../../gcc-5.1.1/libgcc/libgcc2.c:2256:
>>> undefined reference to `__EH_FRAME_BEGIN__'
>>> collect2.exe: error: ld returned 1 exit status
>>> Makefile:947: recipe for target 'libgcc_s.dll' failed
>>>
>>> I'm less experienced with this type of issue so if anyone could give
>>> me some guidance on this before I report the issue, it would be
>>> greatly appreciated.  The issue does not come up unless
>>> "--disable-sjlj-exceptions" is specified during configuration.  This
>>> didn't occur under 4.9.2 and appears new to 5.1.  Full build logs for
>>> libgcc found here:
>>>
>>> http://pastebin.com/xMnZxmbs
>>>
>>> I mainly just want to try and eliminate other possible causes before
>>> creating a bug for it though the same configuration builds fine for
>>> gcc 4.9.2.
>>
>> Just wanted to note that -- according to my observations on IRC and MLs -- 
>> others are hitting the same issue with i686/dw2.
>>
>> --
>> David Macek
>>
>>
>> ------------------------------------------------------------------------------
>> One dashboard for servers and applications across Physical-Virtual-Cloud
>> Widest out-of-the-box monitoring support with 50+ applications
>> Performance metrics, stats and reports that give you Actionable Insights
>> Deep dive visibility with transaction tracing using APM Insight.
>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>> _______________________________________________
>> Mingw-w64-public mailing list
>> Mingw-w64-public@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>>

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to