|
1 | 1 | logfloat |
2 | 2 | ======== |
3 | | -[](https://hackage.haskell.org/package/logfloat) |
| 3 | +[](https://hackage.haskell.org/package/logfloat) |
4 | 4 | [](http://packdeps.haskellers.com/specific?package=logfloat) |
5 | | -[](https://travis-ci.org/wrengr/logfloat) |
| 5 | +[](https://travis-ci.org/wrengr/logfloat) |
6 | 6 | [](https://circleci.com/gh/wrengr/logfloat) |
7 | 7 |
|
8 | 8 | This package provides a type for storing numbers in the log-domain, |
@@ -35,11 +35,11 @@ of the following standard installation methods: |
35 | 35 |
|
36 | 36 | -- With cabal-install and without the source: |
37 | 37 | $> cabal install logfloat |
38 | | - |
| 38 | + |
39 | 39 | -- With cabal-install and with the source already: |
40 | 40 | $> cd logfloat |
41 | 41 | $> cabal install |
42 | | - |
| 42 | + |
43 | 43 | -- Without cabal-install, but with the source already: |
44 | 44 | $> cd logfloat |
45 | 45 | $> runhaskell Setup.hs configure --user |
@@ -77,15 +77,14 @@ bug report (which is resolved in GHC 6.10.2): |
77 | 77 |
|
78 | 78 | ### Windows FFI |
79 | 79 |
|
80 | | -The logfloat package builds and installs cleanly with GHC 8.0 and |
81 | | -later on Windows (without needing Cygwin nor Mingw/Msys), and the |
82 | | -installed package can be used in compiled programs without any |
83 | | -issues. |
| 80 | +The logfloat package builds and installs cleanly with GHC on Windows |
| 81 | +(without needing Cygwin nor Mingw/Msys), and the installed package |
| 82 | +can be used in compiled programs without any issues. |
84 | 83 |
|
85 | | -Prior to GHC 8.0, the package does not work from the GHCi debugger |
86 | | -by default and gives errors like "can't load .so/.DLL for: m (addDLL: |
87 | | -could not load DLL)". This is a long-standing issue with GHCi having |
88 | | -to do with the fact that, on Windows, the so-called "libm" file does |
| 84 | +However, by default, the package does not work from the GHCi debugger |
| 85 | +and gives errors like "can't load .so/.DLL for: m (addDLL: could |
| 86 | +not load DLL)". This is a long-standing issue with GHCi having to |
| 87 | +do with the fact that, on Windows, the so-called "libm" file does |
89 | 88 | not actually contain anything (as it does on POSIX) and the C |
90 | 89 | functions we use are instead placed in `libmingwex.a` (which comes |
91 | 90 | bundled with GHC). The problem is that `ghc` (the compiler) knows |
@@ -169,7 +168,7 @@ If you need to disable the FFI due to issues with not being able |
169 | 168 | to find <math.h>, not having prototypes for functions, or linking |
170 | 169 | errors, be sure *not* to pass -D__USE_FFI__ to the cpp filter for |
171 | 170 | ffihugs. |
172 | | - |
| 171 | + |
173 | 172 | Notably, Hugs installs cpphs under the name "cpphs-hugs" by default. |
174 | 173 | The `which` command will try to resolve the location, assuming it's |
175 | 174 | on your $PATH. If it isn't, then change the --with-cpphs= flag to |
|
0 commit comments