GHC issueshttps://gitlab.haskell.org/ghc/ghc/-/issues2019-07-07T19:14:37Zhttps://gitlab.haskell.org/ghc/ghc/-/issues/1223ghc-6.6: panic! (the 'impossible' happened)2019-07-07T19:14:37Zjupdike@gmail.comghc-6.6: panic! (the 'impossible' happened)ghc-6.6: panic! (the 'impossible' happened)
(GHC version 6.6 for i386-apple-darwin):
> checkKind: adding kind constraint
> t{tv a2M5} \[tv\] \*
> t_a1pL{tv} \[tau\] t_a1pL{tv} \[tau\] ??
Please report this as a GHC bug: http://www....ghc-6.6: panic! (the 'impossible' happened)
(GHC version 6.6 for i386-apple-darwin):
> checkKind: adding kind constraint
> t{tv a2M5} \[tv\] \*
> t_a1pL{tv} \[tau\] t_a1pL{tv} \[tau\] ??
Please report this as a GHC bug: http://www.haskell.org/ghc/reportabug
(Note I have a tar.gz with the offending code but it's not obvious how to attach a file to this ticket. If I can do it then I will upload the code and remove this note.)
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | ------------ |
| Version | 6.6 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | Compiler |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | |
| Architecture | |
</details>
<!-- {"blocked_by":[],"summary":"ghc-6.6: panic! (the 'impossible' happened)","status":"New","operating_system":"","component":"Compiler","related":[],"milestone":"","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"6.6","keywords":[],"differentials":[],"test_case":"","architecture":"","cc":[""],"type":"Bug","description":"ghc-6.6: panic! (the 'impossible' happened)\r\n (GHC version 6.6 for i386-apple-darwin):\r\n checkKind: adding kind constraint\r\n t{tv a2M5} [tv] *\r\n t_a1pL{tv} [tau] t_a1pL{tv} [tau] ??\r\n\r\nPlease report this as a GHC bug: http://www.haskell.org/ghc/reportabug\r\n\r\n(Note I have a tar.gz with the offending code but it's not obvious how to attach a file to this ticket. If I can do it then I will upload the code and remove this note.)","type_of_failure":"OtherFailure","blocking":[]} -->https://gitlab.haskell.org/ghc/ghc/-/issues/1224ghci failed to load2019-07-07T19:14:37Zguestghci failed to loadWorking through [Haskell in 5 steps](http://www.haskell.org/haskellwiki/Haskell_in_5_steps) I attempted to execute ghci after installing [ghc-6.6-i386-apple-darwin.tar.bz2](http://haskell.org/ghc/download_ghc_66.html#macosxintel). The ou...Working through [Haskell in 5 steps](http://www.haskell.org/haskellwiki/Haskell_in_5_steps) I attempted to execute ghci after installing [ghc-6.6-i386-apple-darwin.tar.bz2](http://haskell.org/ghc/download_ghc_66.html#macosxintel). The output was:
```
Douglas $ ghci
/usr/local/bin/ghci: line 12: /usr/local/lib/ghc-6.6: is a directory
/usr/local/bin/ghci: line 12: exec: /usr/local/lib/ghc-6.6: cannot execute: Unknown error: 0
```
Editing /usr/local/bin/ghci-6.6 on line 9:
```
- GHCBIN="$libexecdir";
+ GHCBIN="$libexecdir/ghc-6.6";
```
seems to fix the problem.
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | ------------ |
| Version | 6.6 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | high |
| Resolution | Unresolved |
| Component | GHCi |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | |
| Architecture | Multiple |
</details>
<!-- {"blocked_by":[],"summary":"ghci failed to load","status":"New","operating_system":"","component":"GHCi","related":[],"milestone":"","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"6.6","keywords":["ghci"],"differentials":[],"test_case":"","architecture":"Multiple","cc":[""],"type":"Bug","description":"Working through [http://www.haskell.org/haskellwiki/Haskell_in_5_steps Haskell in 5 steps] I attempted to execute ghci after installing [http://haskell.org/ghc/download_ghc_66.html#macosxintel ghc-6.6-i386-apple-darwin.tar.bz2]. The output was:\r\n\r\n{{{\r\nDouglas $ ghci\r\n/usr/local/bin/ghci: line 12: /usr/local/lib/ghc-6.6: is a directory\r\n/usr/local/bin/ghci: line 12: exec: /usr/local/lib/ghc-6.6: cannot execute: Unknown error: 0\r\n}}}\r\n\r\nEditing /usr/local/bin/ghci-6.6 on line 9:\r\n\r\n{{{\r\n- GHCBIN=\"$libexecdir\";\r\n+ GHCBIN=\"$libexecdir/ghc-6.6\";\r\n}}}\r\n\r\nseems to fix the problem.","type_of_failure":"OtherFailure","blocking":[]} -->https://gitlab.haskell.org/ghc/ghc/-/issues/1225configure of yi generates error message on AMD 64-bit OpenBSD 4.02019-07-07T19:14:36Zguestconfigure of yi generates error message on AMD 64-bit OpenBSD 4.0```
A40:/home/daf/Yi/yi-0.1.0}./configure
checking for ghc... ghc
checking for ghc-pkg... ghc-pkg
checking for hsc2hs... hsc2hs
checking for ghc version... 6.6
checking for value of __GLASGOW_HASKELL__... ghc-6.6: /usr/local/lib/ghc-6.6/...```
A40:/home/daf/Yi/yi-0.1.0}./configure
checking for ghc... ghc
checking for ghc-pkg... ghc-pkg
checking for hsc2hs... hsc2hs
checking for ghc version... 6.6
checking for value of __GLASGOW_HASKELL__... ghc-6.6: /usr/local/lib/ghc-6.6/HSbase.o: unknown architecture
ghc-6.6: panic! (the 'impossible' happened)
(GHC version 6.6 for x86_64-unknown-openbsd):
loadObj: failed
Please report this as a GHC bug: http://www.haskell.org/ghc/reportabug
```6.8.2https://gitlab.haskell.org/ghc/ghc/-/issues/1226Add flags --full-flag-help and --print-docdir2019-07-07T19:14:36ZIan Lynagh <igloo@earth.li>Add flags --full-flag-help and --print-docdirIn the thread starting http://www.haskell.org/pipermail/glasgow-haskell-users/2007-March/012141.html
two new flags are proposed:
A `--full-flag-help` flag, which prints essentially the ghc manpage.
A `--print-docdir` flag:
```
$ ghc -...In the thread starting http://www.haskell.org/pipermail/glasgow-haskell-users/2007-March/012141.html
two new flags are proposed:
A `--full-flag-help` flag, which prints essentially the ghc manpage.
A `--print-docdir` flag:
```
$ ghc --print-docdir
c:/ghc/ghc-6.6/doc/html
```
where there are local docs,
```
$ ghc --print-docdir
http://www.haskell.org/ghc/docs/6.6/html/
```
otherwise (note version specific URL).
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | -------------- |
| Version | 6.6 |
| Type | FeatureRequest |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | Driver |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | Unknown |
| Architecture | Unknown |
</details>
<!-- {"blocked_by":[],"summary":"Add flags --full-flag-help and --print-docdir","status":"New","operating_system":"Unknown","component":"Driver","related":[],"milestone":"6.8 branch","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"6.6","keywords":[],"differentials":[],"test_case":"","architecture":"Unknown","cc":[""],"type":"FeatureRequest","description":"In the thread starting http://www.haskell.org/pipermail/glasgow-haskell-users/2007-March/012141.html\r\ntwo new flags are proposed:\r\n\r\nA `--full-flag-help` flag, which prints essentially the ghc manpage.\r\n\r\nA `--print-docdir` flag:\r\n{{{\r\n$ ghc --print-docdir\r\nc:/ghc/ghc-6.6/doc/html\r\n}}}\r\nwhere there are local docs,\r\n{{{\r\n$ ghc --print-docdir\r\nhttp://www.haskell.org/ghc/docs/6.6/html/\r\n}}}\r\notherwise (note version specific URL).","type_of_failure":"OtherFailure","blocking":[]} -->6.8.2Ian Lynagh <igloo@earth.li>Ian Lynagh <igloo@earth.li>https://gitlab.haskell.org/ghc/ghc/-/issues/1227Crash with biographical profiling on OS X2019-07-07T19:14:36ZJudah JacobsonCrash with biographical profiling on OS XBiographical profiling appears to be broken on OS X v.10.4.8 (PPC). See the below example. I've reproduced this with ghc-6.6 and a darcs pull of the ghc-6.6.1 branch.
Leak.hs:
```
module Main where
loop n = foldr (+) 0 [1..n]
main = ...Biographical profiling appears to be broken on OS X v.10.4.8 (PPC). See the below example. I've reproduced this with ghc-6.6 and a darcs pull of the ghc-6.6.1 branch.
Leak.hs:
```
module Main where
loop n = foldr (+) 0 [1..n]
main = print (loop 100000)
```
Example run:
```
~/tmp/leak: ../ghc-6.6/ghc/compiler/stage2/ghc-inplace --make Leak.hs -prof -debug
[1 of 1] Compiling Main ( Leak.hs, Leak.o )
Linking Leak ...
~/tmp/leak: ./Leak +RTS -hc -RTS
5000050000
~/tmp/leak: ./Leak +RTS -hc -hbvoid -RTS
5000050000
Leak: internal error: ASSERTION FAILED: file ProfHeap.c, line 725
(GHC version 6.6.20070314 for powerpc_apple_darwin)
Please report this as a GHC bug: http://www.haskell.org/ghc/reportabug
Abort trap
```
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | ------------ |
| Version | 6.6 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | Compiler |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | MacOS X |
| Architecture | powerpc |
</details>
<!-- {"blocked_by":[],"summary":"Crash with biographical profiling on OS X","status":"New","operating_system":"MacOS X","component":"Compiler","related":[],"milestone":"","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"6.6","keywords":[],"differentials":[],"test_case":"","architecture":"powerpc","cc":[""],"type":"Bug","description":"Biographical profiling appears to be broken on OS X v.10.4.8 (PPC). See the below example. I've reproduced this with ghc-6.6 and a darcs pull of the ghc-6.6.1 branch.\r\n\r\nLeak.hs:\r\n{{{\r\nmodule Main where\r\n\r\nloop n = foldr (+) 0 [1..n]\r\n\r\nmain = print (loop 100000)\r\n}}}\r\n\r\nExample run:\r\n{{{\r\n~/tmp/leak: ../ghc-6.6/ghc/compiler/stage2/ghc-inplace --make Leak.hs -prof -debug\r\n[1 of 1] Compiling Main ( Leak.hs, Leak.o )\r\nLinking Leak ...\r\n~/tmp/leak: ./Leak +RTS -hc -RTS\r\n5000050000\r\n~/tmp/leak: ./Leak +RTS -hc -hbvoid -RTS\r\n5000050000\r\nLeak: internal error: ASSERTION FAILED: file ProfHeap.c, line 725\r\n\r\n (GHC version 6.6.20070314 for powerpc_apple_darwin)\r\n Please report this as a GHC bug: http://www.haskell.org/ghc/reportabug\r\nAbort trap\r\n}}}","type_of_failure":"OtherFailure","blocking":[]} -->6.8.1Simon MarlowSimon Marlowhttps://gitlab.haskell.org/ghc/ghc/-/issues/1228GHCi freezes in Windows upon pressing Ctrl+C (always, not just under cygwin)2019-07-07T19:14:35ZguestGHCi freezes in Windows upon pressing Ctrl+C (always, not just under cygwin)Start GHCi 6.6. It can be started by double clicking the exe, starting it from cmd or from cygwin; it doesn't matter.
Enter \[1..\], and press Ctrl+C (Ctrl+Break has the same effect). GHCi freezes, and can only be closed from the Window...Start GHCi 6.6. It can be started by double clicking the exe, starting it from cmd or from cygwin; it doesn't matter.
Enter \[1..\], and press Ctrl+C (Ctrl+Break has the same effect). GHCi freezes, and can only be closed from the Windows task manager.
GHCi 6.4 does not freeze on Ctrl+C.
I'm using Windows XP SP2, 32 bit version.
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | ------------ |
| Version | 6.6 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | GHCi |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | |
| Architecture | |
</details>
<!-- {"blocked_by":[],"summary":"GHCi freezes in Windows upon pressing Ctrl+C (always, not just under cygwin)","status":"New","operating_system":"","component":"GHCi","related":[],"milestone":"","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"6.6","keywords":[],"differentials":[],"test_case":"","architecture":"","cc":[""],"type":"Bug","description":"Start GHCi 6.6. It can be started by double clicking the exe, starting it from cmd or from cygwin; it doesn't matter.\r\n\r\nEnter [1..], and press Ctrl+C (Ctrl+Break has the same effect). GHCi freezes, and can only be closed from the Windows task manager.\r\n\r\nGHCi 6.4 does not freeze on Ctrl+C.\r\n\r\nI'm using Windows XP SP2, 32 bit version.","type_of_failure":"OtherFailure","blocking":[]} -->6.8.1https://gitlab.haskell.org/ghc/ghc/-/issues/1229Add min/max handling operations for IntSet/IntMap2019-07-07T19:14:35ZjpbernardyAdd min/max handling operations for IntSet/IntMapMake IntMap/IntSet closer to their non-Int counterparts by providing algorithms for minview/maxview and friends.
The code is tested by the collections package testsuite.
<details><summary>Trac metadata</summary>
| Trac field ...Make IntMap/IntSet closer to their non-Int counterparts by providing algorithms for minview/maxview and friends.
The code is tested by the collections package testsuite.
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | -------------- |
| Version | 6.6 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | libraries/base |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | Unknown |
| Architecture | Multiple |
</details>
<!-- {"blocked_by":[],"summary":"Add min/max handling operations for IntSet/IntMap","status":"New","operating_system":"Unknown","component":"libraries/base","related":[],"milestone":"6.8 branch","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"6.6","keywords":["collections"],"differentials":[],"test_case":"","architecture":"Multiple","cc":[""],"type":"Bug","description":"Make IntMap/IntSet closer to their non-Int counterparts by providing algorithms for minview/maxview and friends.\r\n\r\nThe code is tested by the collections package testsuite.","type_of_failure":"OtherFailure","blocking":[]} -->6.8.1jpbernardyjpbernardyhttps://gitlab.haskell.org/ghc/ghc/-/issues/1230write a safety wrapper around readline2019-07-07T19:14:35ZIan Lynagh <igloo@earth.li>write a safety wrapper around readlineIt would be nice to have a wrapper around the low-level readline functions, providing
the same functions but with types in `MonadIO m => MonadReadline m`. The `IO` monad wouldn't be in this class, but `ReadlineT` would be, and a `withRea...It would be nice to have a wrapper around the low-level readline functions, providing
the same functions but with types in `MonadIO m => MonadReadline m`. The `IO` monad wouldn't be in this class, but `ReadlineT` would be, and a `withReadline` function would handle calling `initialize` etc for you as appropriate.
Inspired by:
http://www.haskell.org/pipermail/haskell-cafe/2006-October/019046.html
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | ----------------- |
| Version | 6.6 |
| Type | FeatureRequest |
| TypeOfFailure | OtherFailure |
| Priority | low |
| Resolution | Unresolved |
| Component | libraries (other) |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | Unknown |
| Architecture | Unknown |
</details>
<!-- {"blocked_by":[],"summary":"write a safety wrapper around readline","status":"New","operating_system":"Unknown","component":"libraries (other)","related":[],"milestone":"⊥","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"6.6","keywords":[],"differentials":[],"test_case":"","architecture":"Unknown","cc":[""],"type":"FeatureRequest","description":"It would be nice to have a wrapper around the low-level readline functions, providing\r\nthe same functions but with types in `MonadIO m => MonadReadline m`. The `IO` monad wouldn't be in this class, but `ReadlineT` would be, and a `withReadline` function would handle calling `initialize` etc for you as appropriate.\r\n\r\nInspired by:\r\nhttp://www.haskell.org/pipermail/haskell-cafe/2006-October/019046.html","type_of_failure":"OtherFailure","blocking":[]} -->⊥https://gitlab.haskell.org/ghc/ghc/-/issues/1232generalise runhaskell to support arbitrary file names, not just those with .{...2019-07-07T19:14:34Zfrederik@ofb.netgeneralise runhaskell to support arbitrary file names, not just those with .{l}hs extensionsThe GHC installation should include an executable (either a binary or e.g. /bin/sh script) which can be used at the top of files with the unix "\#!" mechanism to create an executable script. Malcolm Wallace points out that runhs from the...The GHC installation should include an executable (either a binary or e.g. /bin/sh script) which can be used at the top of files with the unix "\#!" mechanism to create an executable script. Malcolm Wallace points out that runhs from the hmake distribution can be used for this, but it should really be part of GHC.
http://www.haskell.org/pipermail/glasgow-haskell-users/2007-March/012172.html
Now that Simon Marlow (?) has implemented the '-x' option to allow files to use arbitrary extensions, this should be as easy as a 2 or 3 line shell script, although I don't know if runghc recognises -x so maybe there is a bit more work to be done.
I would suggest that the name of the executable be 'runhs-ghc' and that a link should be created called 'runhs' (similar to 'runhaskell'; also included in /etc/alternatives/ in Debian) which can be shared with other compilers/interpreters.
For instance, if runghc recognised -x then the following would work as the contents of runhs-ghc:
\#!/bin/sh
/path/to/runghc -x hs "$@"
(The /path/to/runghc should point to the runghc which is installed at the same time as the above script is installed, so it will not be as simple as copying the script into place - some variable substitution will be needed - I think this is standard practice, see the 'firefox' script on a Linux distro for an example of such binding)
Thanks,
Frederik
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | ---------------------------------------------------------------- |
| Version | 6.6 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | Compiler |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | Malcolm.Wallace@cs.york.ac.uk, glasgow-haskell-users@haskell.org |
| Operating system | Unknown |
| Architecture | Unknown |
</details>
<!-- {"blocked_by":[],"summary":"unix-compatible interpreter needed for ghc (desperately)","status":"New","operating_system":"Unknown","component":"Compiler","related":[],"milestone":"","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"6.6","keywords":[],"differentials":[],"test_case":"","architecture":"Unknown","cc":["Malcolm.Wallace@cs.york.ac.uk","glasgow-haskell-users@haskell.org"],"type":"Bug","description":"The GHC installation should include an executable (either a binary or e.g. /bin/sh script) which can be used at the top of files with the unix \"#!\" mechanism to create an executable script. Malcolm Wallace points out that runhs from the hmake distribution can be used for this, but it should really be part of GHC.\r\n\r\nhttp://www.haskell.org/pipermail/glasgow-haskell-users/2007-March/012172.html\r\n\r\nNow that Simon Marlow (?) has implemented the '-x' option to allow files to use arbitrary extensions, this should be as easy as a 2 or 3 line shell script, although I don't know if runghc recognises -x so maybe there is a bit more work to be done.\r\n\r\nI would suggest that the name of the executable be 'runhs-ghc' and that a link should be created called 'runhs' (similar to 'runhaskell'; also included in /etc/alternatives/ in Debian) which can be shared with other compilers/interpreters.\r\n\r\nFor instance, if runghc recognised -x then the following would work as the contents of runhs-ghc:\r\n\r\n#!/bin/sh\r\n/path/to/runghc -x hs \"$@\"\r\n\r\n(The /path/to/runghc should point to the runghc which is installed at the same time as the above script is installed, so it will not be as simple as copying the script into place - some variable substitution will be needed - I think this is standard practice, see the 'firefox' script on a Linux distro for an example of such binding)\r\n\r\nThanks,\r\n\r\nFrederik","type_of_failure":"OtherFailure","blocking":[]} -->6.10.1https://gitlab.haskell.org/ghc/ghc/-/issues/1233Biographical Profiling of Heap crashes2019-07-07T19:14:34ZguestBiographical Profiling of Heap crasheson my amd 64 Linux machine GHC 6.6.2007012 crashes when performing a biographical profiling (+RTS -hb) with any program.
The programs runs until the end and then there is a segmentation fault.
Fawzi
<details><summary>Trac metadata</sum...on my amd 64 Linux machine GHC 6.6.2007012 crashes when performing a biographical profiling (+RTS -hb) with any program.
The programs runs until the end and then there is a segmentation fault.
Fawzi
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | ------------ |
| Version | 6.6 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | Profiling |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | |
| Architecture | |
</details>
<!-- {"blocked_by":[],"summary":"Biographical Profiling of Heap crashes","status":"New","operating_system":"","component":"Profiling","related":[],"milestone":"","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"6.6","keywords":["Biographical","Profiling"],"differentials":[],"test_case":"","architecture":"","cc":[""],"type":"Bug","description":"on my amd 64 Linux machine GHC 6.6.2007012 crashes when performing a biographical profiling (+RTS -hb) with any program.\r\nThe programs runs until the end and then there is a segmentation fault.\r\n\r\nFawzi","type_of_failure":"OtherFailure","blocking":[]} -->https://gitlab.haskell.org/ghc/ghc/-/issues/1234Shouldn't Q be a Functor?2019-07-07T19:14:34ZEelisShouldn't Q be a Functor?There does not seem to be a Functor instance for the Q monad in Template Haskell.
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | ---------------- |
| Version ...There does not seem to be a Functor instance for the Q monad in Template Haskell.
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | ---------------- |
| Version | 6.6 |
| Type | FeatureRequest |
| TypeOfFailure | OtherFailure |
| Priority | low |
| Resolution | Unresolved |
| Component | Template Haskell |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | Multiple |
| Architecture | Multiple |
</details>
<!-- {"blocked_by":[],"summary":"Shouldn't Q be a Functor?","status":"New","operating_system":"Multiple","component":"Template Haskell","related":[],"milestone":"","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"6.6","keywords":["functor","instance","q"],"differentials":[],"test_case":"","architecture":"Multiple","cc":[""],"type":"FeatureRequest","description":"There does not seem to be a Functor instance for the Q monad in Template Haskell.","type_of_failure":"OtherFailure","blocking":[]} -->https://gitlab.haskell.org/ghc/ghc/-/issues/1235Documentation bug: Control.Monad.Reader2019-07-07T19:14:34ZbjpopDocumentation bug: Control.Monad.ReaderThe current docs for Control.Monad.Reader say:
"Declaration of the Monoid class,and instances for list and functions"
which doesn't appear to be correct.
<details><summary>Trac metadata</summary>
| Trac field | Value ...The current docs for Control.Monad.Reader say:
"Declaration of the Monoid class,and instances for list and functions"
which doesn't appear to be correct.
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | ------------- |
| Version | 6.6 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | Documentation |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | Unknown |
| Architecture | Unknown |
</details>
<!-- {"blocked_by":[],"summary":"Documentation bug: Control.Monad.Reader","status":"New","operating_system":"Unknown","component":"Documentation","related":[],"milestone":"","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"6.6","keywords":[],"differentials":[],"test_case":"","architecture":"Unknown","cc":[""],"type":"Bug","description":"The current docs for Control.Monad.Reader say:\r\n\r\n\"Declaration of the Monoid class,and instances for list and functions\"\r\n\r\nwhich doesn't appear to be correct.","type_of_failure":"OtherFailure","blocking":[]} -->https://gitlab.haskell.org/ghc/ghc/-/issues/1236System.Mem.Weak breaks referential transparency2019-07-07T19:14:33Zdrtomc@gmail.comSystem.Mem.Weak breaks referential transparencyConsider the following two functions:
foo = do
mkWeakPtr y (Just launchMissiles)
return y
where
> y = 42
bar = do
mkWeakPtr 42 (Just launchMissiles)
> return 42
These two functions are equivalent right? After all referenti...Consider the following two functions:
foo = do
mkWeakPtr y (Just launchMissiles)
return y
where
> y = 42
bar = do
mkWeakPtr 42 (Just launchMissiles)
> return 42
These two functions are equivalent right? After all referential transparency means that if y = 42, then anywhere y occurrs I can write 42. The problem is that if I call foo, and hang on to the return value, then launchMissiles won't be called until some time after I stop using the return value, but if I call bar, then launchMissiles may be called any time, including before bar returns!
Looks to me like finalizers break referential transparency, so System.Mem.Weak is broken, though I'm quite willing to be proven wrong.
cheers,
Tom
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | -------------- |
| Version | 6.6 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | libraries/base |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | Unknown |
| Architecture | Unknown |
</details>
<!-- {"blocked_by":[],"summary":"System.Mem.Weak breaks referential transparency","status":"New","operating_system":"Unknown","component":"libraries/base","related":[],"milestone":"","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"6.6","keywords":[],"differentials":[],"test_case":"","architecture":"Unknown","cc":[""],"type":"Bug","description":"Consider the following two functions:\r\n\r\nfoo = do\r\n mkWeakPtr y (Just launchMissiles)\r\n return y\r\n where\r\n y = 42\r\n\r\nbar = do\r\n mkWeakPtr 42 (Just launchMissiles)\r\n return 42\r\n\r\nThese two functions are equivalent right? After all referential transparency means that if y = 42, then anywhere y occurrs I can write 42. The problem is that if I call foo, and hang on to the return value, then launchMissiles won't be called until some time after I stop using the return value, but if I call bar, then launchMissiles may be called any time, including before bar returns!\r\n\r\nLooks to me like finalizers break referential transparency, so System.Mem.Weak is broken, though I'm quite willing to be proven wrong.\r\n\r\ncheers,\r\nTom","type_of_failure":"OtherFailure","blocking":[]} -->https://gitlab.haskell.org/ghc/ghc/-/issues/1237misleading error message from cabal when versions differ2019-07-07T19:14:33Zguestmisleading error message from cabal when versions differUsing cabal, I do './Setup.hs configure', './Setup.hs build', and 'sudo ./Setup.hs install'. Unfortunately, root's $PATH pointed to a different GHC (6.7 at some point, and not 6.4.2 which I was using), which resulted in the error message...Using cabal, I do './Setup.hs configure', './Setup.hs build', and 'sudo ./Setup.hs install'. Unfortunately, root's $PATH pointed to a different GHC (6.7 at some point, and not 6.4.2 which I was using), which resulted in the error message:
> Setup.hs: error reading ./.setup-config; run "setup configure" command?
Of course, there was nothing wrong with .setup-config, so I spent some time investigating permissions, before int-e suggested that the search path was at fault.
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | ------------ |
| Version | 6.7 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | None |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | Unknown |
| Architecture | Unknown |
</details>
<!-- {"blocked_by":[],"summary":"misleading error message from cabal when versions differ","status":"New","operating_system":"Unknown","component":"None","related":[],"milestone":"","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"6.7","keywords":[],"differentials":[],"test_case":"","architecture":"Unknown","cc":[""],"type":"Bug","description":"Using cabal, I do './Setup.hs configure', './Setup.hs build', and 'sudo ./Setup.hs install'. Unfortunately, root's $PATH pointed to a different GHC (6.7 at some point, and not 6.4.2 which I was using), which resulted in the error message:\r\n\r\n Setup.hs: error reading ./.setup-config; run \"setup configure\" command?\r\n\r\nOf course, there was nothing wrong with .setup-config, so I spent some time investigating permissions, before int-e suggested that the search path was at fault.","type_of_failure":"OtherFailure","blocking":[]} -->https://gitlab.haskell.org/ghc/ghc/-/issues/1238ByteString based datagram communication2019-07-07T19:14:33ZrobreimByteString based datagram communicationThis patch adds ByteString datagram communication.
In the process it replaces the TCP based sendTo and recvFrom functions from the Network module with ByteString / datagram equivalents. Since sendTo and recvFrom seemed to be deprecated ...This patch adds ByteString datagram communication.
In the process it replaces the TCP based sendTo and recvFrom functions from the Network module with ByteString / datagram equivalents. Since sendTo and recvFrom seemed to be deprecated for anything more than superficial testing, the new versions would seem more useful.
It includes a fix to ensure Network.Socket.recvBufFrom and friends handle unix file sockets.
net003 has been included for testing the new features. I have only been able to test on GHC 6.6 on linux. Attempts to test with windows and hugs caused me issues I don't currently have time to deal with. If someone with these platforms can apply the patch and run the test case, I'd be very appreciative. I'll get onto any bugs discovered when I return.
I won't be available to guide this bug through for the next 9 days but wanted to get the proposal out there ready for when I get back.
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | ----------------- |
| Version | 6.6 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | libraries/network |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | Unknown |
| Architecture | Unknown |
</details>
<!-- {"blocked_by":[],"summary":"ByteString based datagram communication","status":"New","operating_system":"Unknown","component":"libraries/network","related":[],"milestone":"Not GHC","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"6.6","keywords":[],"differentials":[],"test_case":"","architecture":"Unknown","cc":[""],"type":"Bug","description":"This patch adds ByteString datagram communication.\r\n\r\nIn the process it replaces the TCP based sendTo and recvFrom functions from the Network module with ByteString / datagram equivalents. Since sendTo and recvFrom seemed to be deprecated for anything more than superficial testing, the new versions would seem more useful.\r\n\r\nIt includes a fix to ensure Network.Socket.recvBufFrom and friends handle unix file sockets.\r\n\r\nnet003 has been included for testing the new features. I have only been able to test on GHC 6.6 on linux. Attempts to test with windows and hugs caused me issues I don't currently have time to deal with. If someone with these platforms can apply the patch and run the test case, I'd be very appreciative. I'll get onto any bugs discovered when I return.\r\n\r\nI won't be available to guide this bug through for the next 9 days but wanted to get the proposal out there ready for when I get back.","type_of_failure":"OtherFailure","blocking":[]} -->Not GHChttps://gitlab.haskell.org/ghc/ghc/-/issues/1239compare on exceptional Doubles and Floats should raise an error2019-07-07T19:14:33ZIan Lynagh <igloo@earth.li>compare on exceptional Doubles and Floats should raise an errorConsider:
```
let n = 0/0 :: Double in (n `compare` n, n < n, n == n, n > n)
```
In GHC and YHC this gives
```
(GT,False,False,False)
```
while in hugs it gives
```
(EQ,False,False,False)
```
Neither of these is very satisfactory, ...Consider:
```
let n = 0/0 :: Double in (n `compare` n, n < n, n == n, n > n)
```
In GHC and YHC this gives
```
(GT,False,False,False)
```
while in hugs it gives
```
(EQ,False,False,False)
```
Neither of these is very satisfactory, as I would expect
```
x `compare` y === EQ => (x == y) === True
x `compare` y === GT => (x > y) === True
```
and it's even less pleasant that the implementations differ for no good
reason.
The Haskell report isn't very helpful on how comparing exceptional
Doubles should behave, as it doesn't even say you need to have NaN etc:
```
http://haskell.org/onlinereport/basic.html#sect6.4
The results of exceptional conditions (such as overflow or
underflow) on the fixed-precision numeric types are undefined; an
implementation may choose error (_|_, semantically), a truncated
value, or a special value such as infinity, indefinite, etc.
```
I think that the right answer is that
```
n `compare` n
```
above
(and more generally such a comparison for any incomparable Doubles or Flaots)
should raise an error (i.e. be _\|_).
The changes needed are simple, e.g. for GHC
```
(D# x) `compare` (D# y) | x <## y = LT
| x ==## y = EQ
| otherwise = GT
```
becomes
```
(D# x) `compare` (D# y) | x <## y = LT
| x ==## y = EQ
| x >## y = GT
| otherwise = error "Incomparable values"
```
Deadline: 1 week after discussion ends.
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | -------------- |
| Version | 6.6 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | libraries/base |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | Unknown |
| Architecture | Unknown |
</details>
<!-- {"blocked_by":[],"summary":"compare on exceptional Doubles and Floats should raise an error","status":"New","operating_system":"Unknown","component":"libraries/base","related":[],"milestone":"","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"6.6","keywords":[],"differentials":[],"test_case":"","architecture":"Unknown","cc":[""],"type":"Bug","description":"Consider:\r\n{{{\r\nlet n = 0/0 :: Double in (n `compare` n, n < n, n == n, n > n)\r\n}}}\r\nIn GHC and YHC this gives\r\n{{{\r\n(GT,False,False,False)\r\n}}}\r\nwhile in hugs it gives\r\n{{{\r\n(EQ,False,False,False)\r\n}}}\r\nNeither of these is very satisfactory, as I would expect\r\n{{{\r\nx `compare` y === EQ => (x == y) === True\r\nx `compare` y === GT => (x > y) === True\r\n}}}\r\nand it's even less pleasant that the implementations differ for no good\r\nreason.\r\n\r\nThe Haskell report isn't very helpful on how comparing exceptional\r\nDoubles should behave, as it doesn't even say you need to have NaN etc:\r\n{{{\r\nhttp://haskell.org/onlinereport/basic.html#sect6.4\r\nThe results of exceptional conditions (such as overflow or \r\nunderflow) on the fixed-precision numeric types are undefined; an\r\nimplementation may choose error (_|_, semantically), a truncated\r\nvalue, or a special value such as infinity, indefinite, etc.\r\n}}}\r\nI think that the right answer is that\r\n{{{\r\nn `compare` n\r\n}}}\r\nabove\r\n(and more generally such a comparison for any incomparable Doubles or Flaots)\r\nshould raise an error (i.e. be _|_).\r\n\r\nThe changes needed are simple, e.g. for GHC\r\n{{{\r\n(D# x) `compare` (D# y) | x <## y = LT\r\n | x ==## y = EQ\r\n | otherwise = GT\r\n}}}\r\nbecomes\r\n{{{\r\n(D# x) `compare` (D# y) | x <## y = LT\r\n | x ==## y = EQ\r\n | x >## y = GT\r\n | otherwise = error \"Incomparable values\"\r\n}}}\r\n\r\nDeadline: 1 week after discussion ends.","type_of_failure":"OtherFailure","blocking":[]} -->https://gitlab.haskell.org/ghc/ghc/-/issues/1240Template Haskell only accepts semicolons not newlines in data declaration quo...2019-07-07T19:14:32ZgreenrdTemplate Haskell only accepts semicolons not newlines in data declaration quotationsGHC 6.6 rejects a declaration quotation (i.e. \[\|d ... \|\]) containing multiple lines, but it accepts it if you change all newlines to semicolons. The latter makes code harder to read.
<details><summary>Trac metadata</summary>
| Trac...GHC 6.6 rejects a declaration quotation (i.e. \[\|d ... \|\]) containing multiple lines, but it accepts it if you change all newlines to semicolons. The latter makes code harder to read.
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | ---------------- |
| Version | 6.6 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | low |
| Resolution | Unresolved |
| Component | Template Haskell |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | |
| Architecture | |
</details>
<!-- {"blocked_by":[],"summary":"Template Haskell only accepts semicolons not newlines in declaration quotations","status":"New","operating_system":"","component":"Template Haskell","related":[],"milestone":"","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"6.6","keywords":[],"differentials":[],"test_case":"","architecture":"","cc":[""],"type":"Bug","description":"GHC 6.6 rejects a declaration quotation (i.e. [|d ... |]) containing multiple lines, but it accepts it if you change all newlines to semicolons. The latter makes code harder to read.","type_of_failure":"OtherFailure","blocking":[]} -->https://gitlab.haskell.org/ghc/ghc/-/issues/1241Functional dependency Coverage Condition is lifted, and should not be2019-07-07T19:14:32ZguestFunctional dependency Coverage Condition is lifted, and should not beHello,
GHC 6.6 (with flags `-fglasgow-exts -fallow-undecidable-instances`) is too liberal when accepting instances. Here is an example:
```
class F a b | a -> b where f :: (a,b)
instance F Int b
```
The instance violates the functional...Hello,
GHC 6.6 (with flags `-fglasgow-exts -fallow-undecidable-instances`) is too liberal when accepting instances. Here is an example:
```
class F a b | a -> b where f :: (a,b)
instance F Int b
```
The instance violates the functional dependency constraint of `F` because (in theory) it can be used to solve both `F Int Bool` and `F Int Char`. In practice, it seems that some free variable gets bound upon the first use of `f` with a concrete type, leading to some rather confusing behavior. Example:
```
x :: (Int,a)
x = f
y :: (Int,Bool)
y = f
z :: (Int,Char)
z = x -- works, but 'z = f' does not
```
-Iavorhttps://gitlab.haskell.org/ghc/ghc/-/issues/1242darcs-all needs Bash but has #!/bin/sh2019-07-07T19:14:31ZLuke Maurerdarcs-all needs Bash but has #!/bin/shI get the following error trying to run `./darcs-all get --extra` on Ubuntu Edgy:
```
luke@kryptonitespoon ghc $ ./darcs-all get --extra
[: 126: ==: unexpected operator
warning: adding --partial, to override use --complete
== running da...I get the following error trying to run `./darcs-all get --extra` on Ubuntu Edgy:
```
luke@kryptonitespoon ghc $ ./darcs-all get --extra
[: 126: ==: unexpected operator
warning: adding --partial, to override use --complete
== running darcs get --partial --extra http://darcs.haskell.org/packages/base
darcs failed: unrecognized option `--extra'
```
Note that the "unexpected operator" message always appears, with or without --extra. However, it appears that there's a processing loop that gets skipped because of the error, and so the --extra gets passed on to darcs.
If I change the shebang line to "\#!/bin/bash", it works. My guess is that either the Bash-ism should be removed, or the shebang line should specify Bash.
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | ------------ |
| Version | 6.7 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | Build System |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | |
| Architecture | Unknown |
</details>
<!-- {"blocked_by":[],"summary":"darcs-all needs Bash but has #!/bin/sh","status":"New","operating_system":"","component":"Build System","related":[],"milestone":"","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"6.7","keywords":[],"differentials":[],"test_case":"","architecture":"Unknown","cc":[""],"type":"Bug","description":"I get the following error trying to run `./darcs-all get --extra` on Ubuntu Edgy:\r\n\r\n{{{\r\nluke@kryptonitespoon ghc $ ./darcs-all get --extra\r\n[: 126: ==: unexpected operator\r\nwarning: adding --partial, to override use --complete\r\n== running darcs get --partial --extra http://darcs.haskell.org/packages/base\r\n\r\ndarcs failed: unrecognized option `--extra'\r\n}}}\r\n\r\nNote that the \"unexpected operator\" message always appears, with or without --extra. However, it appears that there's a processing loop that gets skipped because of the error, and so the --extra gets passed on to darcs.\r\n\r\nIf I change the shebang line to \"#!/bin/bash\", it works. My guess is that either the Bash-ism should be removed, or the shebang line should specify Bash.","type_of_failure":"OtherFailure","blocking":[]} -->https://gitlab.haskell.org/ghc/ghc/-/issues/1243Linking error of ALUT2019-07-07T19:14:31ZguestLinking error of ALUTALUT bindings in http://hackage.haskell.org/packages/archive/pkg-list.html
does not work in Windows.
----
"ghc -package ALUT HelloWorld.hs" returns the following error.
C:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Con...ALUT bindings in http://hackage.haskell.org/packages/archive/pkg-list.html
does not work in Windows.
----
"ghc -package ALUT HelloWorld.hs" returns the following error.
C:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+
0x18): undefined reference to `alutInit@8'
C:\Program Files\Haskell\ALUT-2.0\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+
0xdc): undefined reference to `alutInitWithoutContext\@8'
C:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+
0x19d): undefined reference to `alutExit@0'
C:\Program Files\Haskell\ALUT-2.0\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+
0x1d9): undefined reference to `alutGetError\@0'
C:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+
0x210): undefined reference to `alutCreateBufferFromFile@4'
C:\Program Files\Haskell\ALUT-2.0\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+
0x2b0): undefined reference to `alutCreateBufferFromFileImage\@8'
C:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+
0x36d): undefined reference to `alutCreateBufferHelloWorld@0'
C:\Program Files\Haskell\ALUT-2.0\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+
0x3f7): undefined reference to `alutCreateBufferWaveform\@16'
C:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+
0x584): undefined reference to `alutLoadMemoryFromFile@16'
C:\Program Files\Haskell\ALUT-2.0\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+
0x6b8): undefined reference to `alutLoadMemoryFromFileImage\@20'
C:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+
0x7e8): undefined reference to `alutLoadMemoryHelloWorld@12'
C:\Program Files\Haskell\ALUT-2.0\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+
0x92f): undefined reference to `alutLoadMemoryWaveform\@28'
C:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+
0xb2c): undefined reference to `alutGetMIMETypes@4'
C:\Program Files\Haskell\ALUT-2.0\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+
0xbc9): undefined reference to `alutGetMajorVersion\@0'
C:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+
0xc01): undefined reference to `alutGetMinorVersion@0'
C:\Program Files\Haskell\ALUT-2.0\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+
0xc55): undefined reference to `alutSleep\@4'
C:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+
0xd89): undefined reference to \`alutGetErrorString\@4'
collect2: ld returned 1 exit status
----
libHSALUT-2.0.a has a symbol "??@..", but alut.lib does not have "@.." of "??@..". I think this omitting "@.." is a cause of these errors.
environment: Windows XP SP2, MinGW/MSYS, GHC6.6
<details><summary>Trac metadata</summary>
| Trac field | Value |
| ---------------------- | ----------------- |
| Version | 6.6 |
| Type | Bug |
| TypeOfFailure | OtherFailure |
| Priority | normal |
| Resolution | Unresolved |
| Component | libraries (other) |
| Test case | |
| Differential revisions | |
| BlockedBy | |
| Related | |
| Blocking | |
| CC | |
| Operating system | |
| Architecture | Unknown |
</details>
<!-- {"blocked_by":[],"summary":"Linking error of ALUT","status":"New","operating_system":"","component":"libraries (other)","related":[],"milestone":"","resolution":"Unresolved","owner":{"tag":"Unowned"},"version":"6.6","keywords":[],"differentials":[],"test_case":"","architecture":"Unknown","cc":[""],"type":"Bug","description":"ALUT bindings in http://hackage.haskell.org/packages/archive/pkg-list.html\r\ndoes not work in Windows.\r\n\r\n----\r\n\r\n\"ghc -package ALUT HelloWorld.hs\" returns the following error.\r\n\r\nC:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+\r\n0x18): undefined reference to `alutInit@8'\r\n\r\nC:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+\r\n0xdc): undefined reference to `alutInitWithoutContext@8'\r\n\r\nC:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+\r\n0x19d): undefined reference to `alutExit@0'\r\n\r\nC:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+\r\n0x1d9): undefined reference to `alutGetError@0'\r\n\r\nC:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+\r\n0x210): undefined reference to `alutCreateBufferFromFile@4'\r\n\r\nC:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+\r\n0x2b0): undefined reference to `alutCreateBufferFromFileImage@8'\r\n\r\nC:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+\r\n0x36d): undefined reference to `alutCreateBufferHelloWorld@0'\r\n\r\nC:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+\r\n0x3f7): undefined reference to `alutCreateBufferWaveform@16'\r\n\r\nC:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+\r\n0x584): undefined reference to `alutLoadMemoryFromFile@16'\r\n\r\nC:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+\r\n0x6b8): undefined reference to `alutLoadMemoryFromFileImage@20'\r\n\r\nC:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+\r\n0x7e8): undefined reference to `alutLoadMemoryHelloWorld@12'\r\n\r\nC:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+\r\n0x92f): undefined reference to `alutLoadMemoryWaveform@28'\r\n\r\nC:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+\r\n0xb2c): undefined reference to `alutGetMIMETypes@4'\r\n\r\nC:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+\r\n0xbc9): undefined reference to `alutGetMajorVersion@0'\r\n\r\nC:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+\r\n0xc01): undefined reference to `alutGetMinorVersion@0'\r\n\r\nC:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+\r\n0xc55): undefined reference to `alutSleep@4'\r\n\r\nC:\\Program Files\\Haskell\\ALUT-2.0\\ghc-6.6/libHSALUT-2.0.a(Config.o):fake:(.text+\r\n0xd89): undefined reference to `alutGetErrorString@4'\r\n\r\ncollect2: ld returned 1 exit status\r\n\r\n----\r\n\r\nlibHSALUT-2.0.a has a symbol \"??@..\", but alut.lib does not have \"@..\" of \"??@..\". I think this omitting \"@..\" is a cause of these errors. \r\n\r\nenvironment: Windows XP SP2, MinGW/MSYS, GHC6.6","type_of_failure":"OtherFailure","blocking":[]} -->Not GHC