Hello Erik,
2009/9/29 Erik de Castro Lopo <[email protected]>:
> Hi all,
>
> I've created an executable using x86_64-w64-mingw32-g++, but when
> I copy that to another machine, the executable won't run because
> it needs libgcc_s_sjlj-1.dll.
>
> Is there a way to ensure that libgcc_s_sjlj gets compiled statically?
> I tried -static-libgcc which I found in a debian bug report, but
> that didn't help.
>
> Cheers,
> Erik
> --
> ----------------------------------------------------------------------
> Erik de Castro Lopo
> http://www.mega-nerd.com/
The static version is by default present, but to ensure that
multithreades exceptions and exception over DLL boundaries are
working, gcc uses by default the shared version. You can specify on
demand on g++'s command-line the option -static, so only static
libraries are linked, but be aware about the issues I mentioned above.
Cheers,
Kai
--
| (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
