[Bug libgcc/88772] New: Exception handling configured mode does not match the one finally used

2019-01-09 Thread ylatuya at gmail dot com
Priority: P3 Component: libgcc Assignee: unassigned at gcc dot gnu.org Reporter: ylatuya at gmail dot com Target Milestone: --- I am building a multilib GCC+MinGW toolchain targeting Windows. I have built the cross toolchain, which compiled and works

[Bug libgcc/88772] Exception handling configured mode does not match the one finally used

2019-01-09 Thread ylatuya at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88772 --- Comment #2 from Andoni --- (In reply to Eric Botcazou from comment #1) > What's the result of the configure check of libgcc for SJLJ? It should be > visible in the config.log file in the libgcc build directory: > > whether the compiler is c

[Bug libgcc/88772] Exception handling configured mode does not match the one finally used

2019-01-10 Thread ylatuya at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88772 --- Comment #4 from Andoni --- (In reply to Eric Botcazou from comment #3) > > I just wiped the build to start a clean build from scratch, but I remember > > checking this and it was "no". I can confirm it in ~1 hour > > Can you confirm that we'

[Bug libgcc/88772] Exception handling configured mode does not match the one finally used

2019-01-10 Thread ylatuya at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88772 --- Comment #6 from Andoni --- (In reply to Eric Botcazou from comment #5) > > But you said above that the result is "yes" for 32-bit, so how come the test: > > x$ac_cv_sjlj_exceptions = xyes; > > is false? Does it help to rewrite it into j

[Bug libstdc++/89044] New: libstdc++-6.dll is installed in the wrong directory cross-compiling with a multilib configuration

2019-01-24 Thread ylatuya at gmail dot com
: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: ylatuya at gmail dot com Target Milestone: --- When compiling gcc with multilib support for Linux, libstdc++-6.dll ends ups installed correctly

[Bug libstdc++/89044] libstdc++-6.dll is installed in the wrong directory cross-compiling with a multilib configuration

2019-01-25 Thread ylatuya at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89044 --- Comment #2 from Andoni --- 8.2.0 I updated the version field too.

[Bug libstdc++/89044] libstdc++-6.dll is installed in the wrong directory cross-compiling with a multilib configuration

2019-01-25 Thread ylatuya at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89044 --- Comment #4 from Andoni --- I am sorry for now explaining my self good enough. I am building a GCC toolchain for Windows: a cross-compiler one with Linux as host and a native one with Windows as host. Both toolchains are built in a Linux mach

[Bug libstdc++/57212] New: Don't use pe-coff weak support with mingw

2013-05-08 Thread ylatuya at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57212 Bug #: 57212 Summary: Don't use pe-coff weak support with mingw Classification: Unclassified Product: gcc Version: 4.7.4 Status: UNCONFIRMED Severity: major

[Bug libstdc++/57212] Don't use pe-coff weak support with mingw

2013-05-08 Thread ylatuya at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57212 --- Comment #1 from Andoni 2013-05-08 13:40:46 UTC --- Created attachment 30056 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30056 Fix libstdc threads for mingw

[Bug libstdc++/57212] Don't use pe-coff weak support with mingw

2013-05-08 Thread ylatuya at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57212 Andoni changed: What|Removed |Added Attachment #30056|0 |1 is obsolete|