Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation of SML/NJ 2021.1 fails on Ubuntu 20.04 #233

Closed
1 of 5 tasks
JohnReppy opened this issue Jul 16, 2022 · 7 comments
Closed
1 of 5 tasks

Installation of SML/NJ 2021.1 fails on Ubuntu 20.04 #233

JohnReppy opened this issue Jul 16, 2022 · 7 comments
Assignees
Labels
bug Something isn't working fixed-in-2023.1 Issues that are addressed in the 2023.1 release gforge bug (or feature request) ported from smlnj-gforge repository installation problem with installation

Comments

@JohnReppy
Copy link
Contributor

Version

2021.1

Operating System

  • All
  • Linux
  • macOS
  • Windows
  • Other Unix

OS Version

Ubuntu 20.04

Processor

x86 (32-bit)

Component

Installation

Severity

No response

Description of the problem

Installing SML/NJ 2021.1 on Ubuntu 20.04 fails, raising exception CFunNotFound with "CodeGen.setTarget". (Curiously, the same installation procedure seems to succeed on macOS.)

Transcript

...
                            := = :=
                             ! = !
                        cthrow = throw
                       isolate = isolate
                       capture = capture
                         throw = throw
                        callcc = callcc
********************
/home/user/Downloads/nj-2021.1/bin/.run/run.amd64-linux: Fatal error -- Uncaught exception CFunNotFound with "CodeGen.setTarget" raised at Basis/Implementation/Unsafe/cinterface.sml:24.19-24.72

config/install.sh !!! Boot code failed, no heap image (sml.amd64-linux).

Expected Behavior

No response

Steps to Reproduce

config/install.sh
(run on Ubuntu 20.04)

Additional Information

No response

Email address

No response

Comments from smlnj-gforge

Original smlnj-gforge bug number 300

Submitted on 2022-54-02 at 18:5400

comment by @JohnReppy on 2022-27-31 16:2700 +000 UTC

This appears to be a problem with the in-memory object file produced by LLVM on Linux.

@JohnReppy JohnReppy added bug Something isn't working gforge bug (or feature request) ported from smlnj-gforge repository installer labels Jul 16, 2022
@JohnReppy JohnReppy self-assigned this Jul 16, 2022
@JohnReppy JohnReppy added installation problem with installation and removed installer labels Jul 16, 2022
@dmacqueen
Copy link
Contributor

dmacqueen commented Aug 4, 2022 via email

@haijinSk
Copy link

haijinSk commented Aug 7, 2022

Thank you very much. I appreciate your response and effort. Yes, my installation is still integer only, so to speak, but I will try future versions of SML/NJ and anyway, at some point, I will buy new or newer computer, with more fitting CPU, concerning the floats, I'm sure. Though, the true is, right now, I have installed some other programming languages, the newest versions, without the float problem. I think, and I'm not good at low-level things, but I see it that If in my installation process there is no pre-built binary or there is no assembly code not fitting my CPU, then indeed, it's very hard to suggest something, even to point to something. Anyway thank you.

@JohnReppy
Copy link
Contributor Author

JohnReppy commented Oct 11, 2022 via email

@haijinSk
Copy link

John, sir, thank you, very, very much...

I didn't try 32-bit version yet, but according to the shell command it seems that my CPU have "ssse3" (if it means the "SSE-3"), and "sse2" as well.

Thank you.

Peter

@haijinSk
Copy link

haijinSk commented Aug 8, 2023

For the record, so to speak, now (version: 64-bit v110.99.4 on Ubuntu 22.04.3) with newer hardware (including the key thing: a newer processor) it seems that my problem with non-integer numbers has gone. I won't test this new version of SMLNJ on my old "problematic" hardware, so I don't know if it has something to do with my new processor, but anyway, thank you very much for the language.

@JohnReppy
Copy link
Contributor Author

Glad to hear that it is working for you.

@JohnReppy
Copy link
Contributor Author

The problems with the LLVM-based backend own Linux were owing to complications in the way that the ELF object-file format treats relocation. These have now been fixed and the system bootstraps on Linux and can compile itself.

@JohnReppy JohnReppy added the fixed-in-2023.1 Issues that are addressed in the 2023.1 release label Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fixed-in-2023.1 Issues that are addressed in the 2023.1 release gforge bug (or feature request) ported from smlnj-gforge repository installation problem with installation
Projects
None yet
Development

No branches or pull requests

3 participants