2013/8/8 LRN :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 07.08.2013 22:37, Michael Cronenworth wrote:
>> On 08/07/2013 01:35 PM, LRN wrote:
>>> What does "might" mean there? Like, you may get a dependency, or you may
>>> not? It doesn't sound like you ALWAYS get a dependency.
>>> Pre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07.08.2013 22:37, Michael Cronenworth wrote:
> On 08/07/2013 01:35 PM, LRN wrote:
>> What does "might" mean there? Like, you may get a dependency, or you may
>> not? It doesn't sound like you ALWAYS get a dependency.
>> Previously you WOULD get the
On 08/07/2013 01:35 PM, LRN wrote:
> What does "might" mean there? Like, you may get a dependency, or you may
> not? It doesn't sound like you ALWAYS get a dependency.
> Previously you WOULD get the dependency if you had code that required
> it, and WOULD NOT get it otherwise.
> Now you get it rega
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07.08.2013 22:22, Michael Cronenworth wrote:
> On 08/07/2013 01:16 PM, LRN wrote:
>> So...what changed? Why is libgcc now mandatory for any library
>> (including empty dlls)? Is that a problem in my toolchain only, or is
>> everyone experiencing it?
On 08/07/2013 01:16 PM, LRN wrote:
> So...what changed? Why is libgcc now mandatory for any library
> (including empty dlls)? Is that a problem in my toolchain only, or is
> everyone experiencing it?
Yes, and the change is intended.
See: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57120
---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Recently i've discovered that all dlls i've built are linked to
libgcc_s_sjlj-1.dll
They import these functions:
__udivdi3
__umoddi3
This didn't happen before.
What did happen is that libgcc would be a dependency only for
libraries/programs that requi
