2013/7/19 Alexpux
>
> 16.07.2013, в 0:44, Ruben Van Boxem написал(а):
>
> 2013/7/15 Earnie Boyd
>
>> On Mon, Jul 15, 2013 at 2:09 PM, Alexey Pavlov wrote:
>> > 2013/7/15 Jon :
>> >> On Mon, 15 Jul 2013 11:02:20 +0400
>> >> niXman wrote:
>> >>
>> >>> 2013/7/15 Jon:
>> >>> > When I build C apps w
16.07.2013, в 0:44, Ruben Van Boxem написал(а):
> 2013/7/15 Earnie Boyd
> On Mon, Jul 15, 2013 at 2:09 PM, Alexey Pavlov wrote:
> > 2013/7/15 Jon :
> >> On Mon, 15 Jul 2013 11:02:20 +0400
> >> niXman wrote:
> >>
> >>> 2013/7/15 Jon:
> >>> > When I build C apps with mingwbuilds 4.8.1-win32-sjlj,
2013/7/16 Ruben Van Boxem:
> Why not just add -static to the link flags for the GCC executables? You can
> do this through LDFLAGS (I think) or abuse --with-host-libstdc++ for it.
> This makes any GCC compiler executable independent of dll's of the toolchain
> used to build it.
Already used:
http
2013/7/15 Earnie Boyd
> On Mon, Jul 15, 2013 at 2:09 PM, Alexey Pavlov wrote:
> > 2013/7/15 Jon :
> >> On Mon, 15 Jul 2013 11:02:20 +0400
> >> niXman wrote:
> >>
> >>> 2013/7/15 Jon:
> >>> > When I build C apps with mingwbuilds 4.8.1-win32-sjlj, the built
> artifacts have a runtime dependency on
On Mon, Jul 15, 2013 at 2:09 PM, Alexey Pavlov wrote:
> 2013/7/15 Jon :
>> On Mon, 15 Jul 2013 11:02:20 +0400
>> niXman wrote:
>>
>>> 2013/7/15 Jon:
>>> > When I build C apps with mingwbuilds 4.8.1-win32-sjlj, the built
>>> > artifacts have a runtime dependency on
>>> > `libgcc_s_sjlj-1.dll`. This
2013/7/15 Jon :
> On Mon, 15 Jul 2013 11:02:20 +0400
> niXman wrote:
>
>> 2013/7/15 Jon:
>> > When I build C apps with mingwbuilds 4.8.1-win32-sjlj, the built artifacts
>> > have a runtime dependency on
>> > `libgcc_s_sjlj-1.dll`. This is not the case when I use the rubenvb
>> > toolchains.
>>
>
On Mon, 15 Jul 2013 11:02:20 +0400
niXman wrote:
> 2013/7/15 Jon:
> > When I build C apps with mingwbuilds 4.8.1-win32-sjlj, the built artifacts
> > have a runtime dependency on
> > `libgcc_s_sjlj-1.dll`. This is not the case when I use the rubenvb
> > toolchains.
>
> Just now I checked with [
2013/7/15 Ruben Van Boxem:
> Let's get some things cleared out:
> 1) you can link libgcc statically by adding -static-libgcc to the link
> command. There is also a -static-libstdc++ to go with it IIANM.
> 2) libgcc is not C++ only. You do need the dll version for exceptions to
> work right, althou
2013/7/15 niXman
> 2013/7/15 Jon:
> > When I build C apps with mingwbuilds 4.8.1-win32-sjlj, the built
> artifacts have a runtime dependency on
> > `libgcc_s_sjlj-1.dll`. This is not the case when I use the rubenvb
> toolchains.
>
> Just now I checked with [1] and [2] and found no dependency on
>
2013/7/15 Jon:
> When I build C apps with mingwbuilds 4.8.1-win32-sjlj, the built artifacts
> have a runtime dependency on
> `libgcc_s_sjlj-1.dll`. This is not the case when I use the rubenvb toolchains.
Just now I checked with [1] and [2] and found no dependency on
`libgcc_s_sjlj-1.dll`
What am
When I build C apps with mingwbuilds 4.8.1-win32-sjlj, the built artifacts have
a runtime dependency on
`libgcc_s_sjlj-1.dll`. This is not the case when I use the rubenvb toolchains.
My understanding is that the `libgcc_s_sjlj-1.dll` dependency is only required
for C++, not C, apps due
to except
11 matches
Mail list logo
