[nem-bug] [Nemerle 0000766]: stage1 error: method System.IO.FileStream.Dispose(disposing : bool) : void is not accessible

feedback at nemerle.org feedback at nemerle.org
Tue Sep 26 18:25:19 CEST 2006


The following issue has been RESOLVED.
======================================================================
<http://nemerle.org/bugs/view.php?id=766> 
======================================================================
Reported By:                ildar
Assigned To:                malekith
======================================================================
Project:                    Nemerle
Issue ID:                   766
Category:                   Compiler
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     resolved
Resolution:                 not an issue
Fixed in Version:           
======================================================================
Date Submitted:             09-26-2006 06:48 CEST
Last Modified:              09-26-2006 18:25 CEST
======================================================================
Summary:                    stage1 error: method
System.IO.FileStream.Dispose(disposing : bool) : void is not accessible
Description: 
Self compilation failed on stage1. I checked monodis --method mscorlib.dll
and I see that 
System.IO.FileStream.Dispose(disposing : bool) : void 
is there. What more can I do for the problem to be emerged?
======================================================================

----------------------------------------------------------------------
 malekith - 09-26-06 10:20 
----------------------------------------------------------------------
You can try to upgrade (mono, to development version and/or Nemerle to SVN
version).

0.9.3 should work with 1.1.13, so I'm not sure what is wrong....

----------------------------------------------------------------------
 ildar - 09-26-06 14:47 
----------------------------------------------------------------------
upgrade to 1.1.13.6-alt1 has solved the problem. You can close the issue as
"will be fixed in next release" and make stronger dependence: to 1.1.13.6
mono release.

----------------------------------------------------------------------
 malekith - 09-26-06 18:25 
----------------------------------------------------------------------
Resolving as per OP request.

It's hard to raise requirements for the released version (as in
./configure check). We will probably raise requirements to 1.1.16 or .17
in next release anyway.

Issue History
Date Modified  Username       Field                    Change              
======================================================================
09-26-06 06:48 ildar          New Issue                                    
09-26-06 10:20 malekith       Note Added: 0001455                          
09-26-06 14:47 ildar          Note Added: 0001456                          
09-26-06 18:25 malekith       Status                   new => resolved     
09-26-06 18:25 malekith       Resolution               open => not an issue
09-26-06 18:25 malekith       Assigned To               => malekith        
09-26-06 18:25 malekith       Note Added: 0001458                          
======================================================================




More information about the bugs mailing list