Bug 438934 – dev-lang/smlnj-110.75 - unexpected exception (bug?) in SML/NJ: Io [Io: openIn failed on "/tmp/portage/dev-lang/smlnj-110.75/work/sml.boot.x86-unix/smlnj/.cm/x86-unix/cm.cm", No such file or directory]

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description José Romildo Malaquias 2012-10-19 15:11:30 UTC]

When compiling a SML project, the compiler manager (CM) fails with the message below:


- CM.make "sources.cm";
[autoloading]

unexpected exception (bug?) in SML/NJ: Io [Io: openIn failed on "/tmp/portage/dev-lang/smlnj-110.75/work/sml.boot.x86-unix/smlnj/.cm/x86-unix/cm.cm", No such file or directory]
  raised at: Basis/Implementation/IO/bin-io-fn.sml:617.25-617.71
             ../cm/util/safeio.sml:30.11
             ../compiler/TopLevel/interact/evalloop.sml:44.55


It seems that the temporary location used to install the package when building it has been hard coded into the system.

[Comment 1 Marijn Schouten (RETIRED) 2012-10-22 07:35:18 UTC]

Created attachment 327128 [details]
smlnj-110.75.ebuild

Hi Jose,

in fixing bug 248162, I changed the way smlnj executables are installed. To verify that hypothesis could you test with the attached ebuild and see if it helps? It would also help if you could provide a simple test case.

Marijn

[Comment 2 José Romildo Malaquias 2012-10-22 09:38:54 UTC]

(In reply to comment #1)
> Created attachment 327128 [details]
> smlnj-110.75.ebuild
> 
> Hi Jose,
> 
> in fixing bug 248162, I changed the way smlnj executables are installed. To
> verify that hypothesis could you test with the attached ebuild and see if it
> helps? It would also help if you could provide a simple test case.
> 
> Marijn

I had downgraded to smlnj-110.71 which works. In order to provide a simple test case, I have upgraded to smlnj-110.75 from portage again. This time I am getting another issue (that did not happend before) when launching sml:

$ sml 
/usr/bin/sml: line 60: /usr/libexec/.arch-n-opsys: No such file or directory
sml: unable to determine architecture/operating system

I have also tried the attached ebuild and it works.

[Comment 3 Marijn Schouten (RETIRED) 2012-10-22 12:16:19 UTC]

I am also getting that same error now. Looks like I fumbled when testing. Anyway, I've now committed the attached ebuild which you've confirmed works for you. Thanks for testing and let me know if anything else comes up.