On 3/2/2016 18:55, Mateusz wrote:
> I don't have access rights to apply.
>
> If you have ready patch that enables __MINGW_CTOR_LIST__ only when
> building with clang it will be the best solution before release of ver.
> 5. If not, please revert this commit -- you have the access rights.
>
I don't have access rights to apply.
If you have ready patch that enables __MINGW_CTOR_LIST__ only when
building with clang it will be the best solution before release of ver.
5. If not, please revert this commit -- you have the access rights.
Mateusz
W dniu 2016-03-01 o 21:31, Martell
On 3/2/2016 04:25, Mateusz wrote:
> Hi,
>
> I think we should revert commit [ca451a] Handle __CTOR_LIST__ internally
> within mingw-w64
>
> It is not ready yet and makes serious problems for GCC.
>
Go ahead, thanks.
0xD4EBC740.asc
Description: application/pgp-keys
signature.asc
I can confirm, that gcc5.3.0 also fails with this commit, see
https://github.com/mingwpy/mingwpy/issues/7.
carl
2016-03-01 21:31 GMT+01:00 Martell Malone :
> You have my go ahead to apply.
>
> There is a header setting for when building gcc or rather libgcc to
> specify
You have my go ahead to apply.
There is a header setting for when building gcc or rather libgcc to specify
that ctors and dtors are provided by the c runtime.
This is usually enabled for some embedded targets.
Alternatively I could only enable that when we build the crt with clang and
not gcc.
Hi,
I think we should revert commit [ca451a] Handle __CTOR_LIST__ internally
within mingw-w64
It is not ready yet and makes serious problems for GCC.
Mateusz
diff --git a/mingw-w64-crt/crt/gccmain.c b/mingw-w64-crt/crt/gccmain.c
index ba50691..fc0e350 100644
---