Package Details: lfortran 0.35.0-1

Git Clone URL: https://aur.archlinux.org/lfortran.git (read-only, click to copy)
Package Base: lfortran
Description: Modern interactive LLVM-based Fortran compiler
Upstream URL: https://lfortran.org
Keywords: fortran
Licenses: BSD-3-Clause
Submitter: ciappi
Maintainer: carlosal1015
Last Packager: carlosal1015
Votes: 6
Popularity: 0.40
First Submitted: 2021-11-06 14:37 (UTC)
Last Updated: 2024-04-17 00:33 (UTC)

Latest Comments

1 2 Next › Last »

carlosal1015 commented on 2024-03-30 22:48 (UTC)

Thanks for heads up. Let's await for a patch.

dringsim commented on 2024-03-30 16:29 (UTC)

Currently lfortran doesn't support llvm 17: https://github.com/lfortran/lfortran/issues/2835

xantares commented on 2024-01-02 19:09 (UTC)

kokkos is needed for the cpp backend and could be added as optdepends

ciappi commented on 2023-02-04 08:47 (UTC)

I don't know about GitHub actions, however it should compile with makepkg... I tried to build with llvm15 but I got an error in the tests. I'll investigate into this but, for now, I think it should be usable as it is

carlosal1015 commented on 2023-02-01 20:53 (UTC) (edited on 2023-02-01 21:03 (UTC) by carlosal1015)

Hi, when I compile the package using GitHub Actions runners, I look this error because is some related with different CPUs.

$ lfortran  --version
Illegal instruction

I am not sure if some cmake flags could be turn on/off for fix the issue. I will use in the same host for avoid the error

Edited: could be a dependcy llvm15 or later?

carlosal1015 commented on 2023-01-31 13:54 (UTC) (edited on 2023-01-31 18:49 (UTC) by carlosal1015)

Hi @ciappi, why xeus2 and not xeus?

Edited: I guess I found the answer, only xeus2 is supported.

ciappi commented on 2023-01-30 19:30 (UTC)

Hi @carlosal1015, now it should support using jupyter-notebook. Any feedback is appreciated.

carlosal1015 commented on 2023-01-24 22:33 (UTC)

Hi, how could I get working with jupyter-notebook?

ciappi commented on 2022-10-31 19:12 (UTC)

Updated to 0.18 (I missed the new github repo). For what I can tell, llvm11 is used to compile lfortran itself while clang is used just as a linker (you can use gcc with the option --link-with-gcc). However I've added clang as a dependency since it is the default. This distribution is intended to ship only the default llvm backend. I hope it is usable now.

everythingfunct commented on 2022-10-31 15:27 (UTC)

That allowed it to build, but the llvm backend does not work once installed. I get an error like:

$ lfortran hello.f90
sh: line 1: clang: command not found
The command 'clang -o a.out a.out.tmp.o  -L"/usr/bin/../share/lfortran/lib" -Wl,-rpath,"/usr/bin/../share/lfortran/lib" -llfortran_runtime -lm' failed.

I think it points to something still being misconfigured, either in the PKGBUILD, or lfortran's build system.

The error message from using makepkg is coming from the wasm backend, but I don't believe the clean chroot method built the wasm backend, and hence didn't encounter the error. Is this distribution intended to include the wasm backend? If not, what about my environment is causing it to try and be included?

The message about missing clang is true (it's not installed on my system), but the PKGBUILD doesn't list it as a dependency, and there's not a version available in official repos that would be compatible with the listed requirement of llvm11. So do we really still need to stick to llvm11, or could we just list both llvm and clang?