Hi, I have a C app (Strawberry Perl) built using the 64-bit gcc-4.4.7 compiler.
Whenever that perl starts up it loads libgcc_s_sjlj-1.dll. If I were to replace that 4.4.7 version of libgcc_s_sjlj-1.dll that it loads with a 4.7.0 version of libgcc_s_sjlj-1.dll, would that be something that: a) only an idiot or a moron would even contemplate doing; b) will probably cause problems at some stage; c) you might just get away with; d) won't cause any problems at all because 4.7.0 is later than 4.4.7. By way of brief explanation: I have some x64 perl binaries, and their perl dll's need to load the 4.7.0 libgcc_s_sjlj-1.dll - but they always use the 4.4.7 libgcc_s_sjlj-1.dll (because it has already been loaded by Strawberry perl itself). This results in an unfound entry point error. Having Strawberry perl instead load the 4.7.0 libgcc_s_sjlj-1.dll seems to work ... but at what risk, I wonder. I keep thinking that, even though it works ok for the things I've been doing, there's probably something nasty just waiting to bite. Better if someone knows of a way to have Strawberry Perl stick to loading the correct (4.4.7) libgcc_s_sjlj-1.dll, but still allow these perl dll files to load the 4.7.0 libgcc_s_sjlj-1.dll . Cheers, Rob ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
