First, I start GHCi with a memory card insert in the slot of the computer. GHCi run ok.
Second, I stop running GHCi and I remove the memory card.
Third, I restart GHCi and a message appears in a window "realgcc.exe there is no disk - insert a disk in drive D:". When I reinsert the memory card, GHCi run again.
Realgcc.exe is in the directory c:ghc-8.0.2\mingw\bin.
Hope this help!
Trac metadata
Trac field
Value
Version
8.0.2
Type
Bug
TypeOfFailure
OtherFailure
Priority
normal
Resolution
Unresolved
Component
GHCi
Test case
Differential revisions
BlockedBy
Related
Blocking
CC
Operating system
Architecture
x86
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related or that one is blocking others.
Learn more.
Are you sure that message didn't come from a console that was cd'ed into a folder on the removable drive?
What were you doing with the drive? I don't quite understand what the memory card has to do with he bug report. Were you trying to open files on it before?
Have you checked the sequences I wrote in order the first time?\\
I did it again by doing this:\\
1 - I start the computer in MS-DOS mode without failure with the memory
card install in drive D.\\
2 - I run GHCi; it is ok.\\
3 - I stop GHCi.\\
4 - I remove the memory card.\\
5 - I restart GHCi. GHCi start and stops suddendly when a window appears on the screen. We read the error message in this window.\\
6 - I insert the memory card and click on the button cancel or continue or restart and GHCi works again.\\
or,
1 - I start the computer in MS-DOS mode without failure without memory
card.\\
2 - I run GHCi; it is ok.\\
3 - I stop GHCi.\\
4 - I insert the memory card in drive D\\
5 - I run GHCi; it is ok.\\
6 - I stop GHCi.\\
7 - I remove the memory card.\\
8 - I restart GHCi. GHCi start and stop suddendly when a window appears on the screen. We read the error message in this window.\\
9 - I insert the memory card and click on the button cancel or continue or restart and GHCi works again.\\
Please, apply the check list.\\
I don't know what to say more.\\
Hope this help!
Sorry, I've tried reproducing this and I can plug and remove the memory card but GHCi keeps working fine.
I don't understand why GHCi would be using the card at all. In all likeliness this error is coming from a different process. GHC as a whole never produces errors using messageboxes, so this error does not originate from it.
It is also a standard Windows error produced by explorer. So I will close the ticket as invalid. However if you can show the error does somehow come from GHCi then please re-open.
If the issue is not GHC, the issue comes from the package Haskell platform for Windows.\\
Seemingly the issue comes from realgcc.exe, and realgcc is part of mingw in ghc-8.0.2 directory.\\
In your computer GHCi works fine and it is not broken by that instead of mine.\\
What computer do you prefer to work with GHCi?\\
Give me your e-mail and I send to you a screenshot.
This seems to be an issue with how GCC was configured. It has a hardcoded path that happens to coincide with the path of your memory card[1][2]. Easiest way around this is to change the drive letter of the memory card to something else.
It seems that the GCC in GHC 8.0.1 and GHC 8.0.2 were built on a path D:\develop. This path ended up being hard coded into the binary and it's checked when compiling things.
Because of this, you guys with D:\ mapped to a removable drive get the dialog. This is a bit out of our control. But it seems that the GCC that will be used for the upcoming GHC 8.2 release uses C:\building. Since in 99% of the cases everyone has a fixed drive on C:\ if it's available, then it should work.
So for now, I can recommend a workaround of changing the removable storage from D:\ to something else, or wait for GHC 8.2.1.
This is about as fixed as it's going to get. We'll try to keep an eye out in the future for what the build directory is. But we don't build GCC.