haskell / mwc-random

A very fast Haskell library for generating high quality pseudo-random numbers.
http://hackage.haskell.org/package/mwc-random
BSD 2-Clause "Simplified" License
54 stars 25 forks source link

Linker error when using mwc-random #54

Closed vagarenko closed 4 years ago

vagarenko commented 8 years ago

When trying to compile a package which depends on mwc-random-0.13.4.0. I'm getting this error:

...\.cabal-sandbox\i386-windows-ghc-7.10.2\mwc-random-0.13.4.0-
IZNPKV7FK5fI4SNfIqKUW6/libHSmwc-random-0.13.4.0-
IZNPKV7FK5fI4SNfIqKUW6_p.a(MWC.p_o):fake:(.text+0x164a): undefined reference to 
`SystemFunction036@8'
collect2: ld returned 1 exit status

Windows 7 GHC version 7.10.2, 32 bit.

mwc-random-0.13.3.2 works fine.

Shimuuar commented 8 years ago

Looks like issue was introduced in #52. As a workaround you can use 0.13.3.2

@thoughtpolice which windows did you use to test #52?

thoughtpolice commented 8 years ago

I did this on Windows 10. But SystemFunction036 should be around, like all the time since forever.

thoughtpolice commented 8 years ago

This also might be a bug with GHC 7.10 which has an updated Windows toolchain, which I find more likely (GHC ships a gcc toolchain that should be the same on any platform, so linker errors for stuff like "I'm running Windows 7, not 10" shouldn't occur, since the binaries are the exact same).

joeyh commented 7 years ago

Having same problem on windows here. mwc-random-0.13.3.2 worked.

Shimuuar commented 7 years ago

Which windows do you use and how did you install haskell?

joeyh commented 7 years ago

Aleksey Khudyakov wrote:

Which windows do you use and how did you install haskell?

I don't administer that Windows system myself, but I belive it is windows-7-pro-x86_64 and haskell was installed from the HP, I belive in October 2015. ghc version 7.10.2-a.

see shy jo

patrickt commented 5 years ago

I’ve encountered this on macOS with Stackage LTS 12.0. Pinning to 0.13.3.2 also worked.

Shimuuar commented 4 years ago

I have no way to reproduce this and it was 4 years since issue was opened. So closing

Feel free to reopen/create new issue if you still has this problem.