Re: [Mingw-w64-public] libgcc_s_sjsj-1.dll

2010-05-05 Thread JonY
On 5/6/2010 08:12, Jarrod Chesney wrote: pavel wrote: On Tue, 2010-05-04 at 13:26 +0200, pavel wrote: why the latest release links the programs with the libgcc_s_sjsj-1.dll? Is it possible to avoid that? I have figured this out already. Just for the record, how do you avoid this? You

[Mingw-w64-public] libgcc_s_sjsj-1.dll

2010-05-04 Thread pavel
Hi, why the latest release links the programs with the libgcc_s_sjsj-1.dll? Is it possible to avoid that? Thanks, Pavel -- ___ Mingw-w64-public mailing list

Re: [Mingw-w64-public] libgcc_s_sjsj-1.dll

2010-05-04 Thread pavel
I have figured this out already. Thanks, Pavel On Tue, 2010-05-04 at 13:26 +0200, pavel wrote: Hi, why the latest release links the programs with the libgcc_s_sjsj-1.dll? Is it possible to avoid that? Thanks, Pavel

Re: [Mingw-w64-public] libgcc_s_sjsj-1.dll

2010-05-04 Thread Prof Brian Ripley
On Tue, 4 May 2010, NightStrike wrote: The default changed in 4.4.0, I believe. Use gcc -static to avoid. That does a lot more than stop linking to that one DLL. I'd say you meant -static-libgcc. Note the strictures in 'man gcc' about reasons why that might not be a good idea for C++ and