Julia

W

web9452

Ok I think an executable compatible with FreeBSD is available. But there may be a bunch of dependencies required. I think you can tell I don't have any experience doing this but there is a wrinkle that makes it even harder: I don't have internet. does anybody know how I would approach putting Julia on my box without internet(OS BSD12).
 
lang/julia. Though, you may have to put this package and dependency packages on a usb disk or other medium from a working internet connection, then transfer the packages to a /usr/local/ and perhaps var directories to your computer.
 
Julia download page mentions that v1.11 is for 13.2+. So even if downloading the full source tarball with dependencies from the download page (scroll down), I do not know if it will successfully build.

Searching the internet, I see that v1.7.x seemed to be the earliest version supported in FBSD 12 - speculating based on this old announcement. Unclear at which Julia version support for FBSD 12 got dropped, but here is the GH page that contains the full source tar for v1.7.3.

Note: I do not do Julia. Was just curious and had some time on hand to browse around.
 
domon said:
Julia download page mentions that v1.11 is for 13.2+. So even if downloading the full source tarball with dependencies from the download page (scroll down), I do not know if it will successfully build.

Searching the internet, I see that v1.7.x seemed to be the earliest version supported in FBSD 12 - speculating based on this old announcement. Unclear at which Julia version support for FBSD 12 got dropped, but here is the GH page that contains the full source tar for v1.7.3.

Note: I do not do Julia. Was just curious and had some time on hand to browse around.
Click to expand...
I see your point about FreeBSD 12. the whole thing seems shaky. can you define tarball?
 
sidetone said:
lang/julia. Though, you may have to put this package and dependency packages on a usb disk or other medium from a working internet connection, then transfer the packages to a /usr/local/ and perhaps var directories to your computer.
Click to expand...
moving the dependencies to a thumb drive. may be really time consuming. Does fetch do it automatically.
 
Very interesting. I think I would try to use a thumb drive. Maybe a CD? You mention FETCH. But fetch is BSD??? So i would have to use a laptop with BSD on it and go to coffee shop where I can get an internet connection or go there with a version 12 INSTL disc and run the OS off the INSTL disc and access fetch that way. Do you know if version 12 OS is available so i
could copy it to a disc? Or I would have get a program to mimic FETCH on windows. All of this would be a great learning experience but might have unforeseen difficulties?
 
Tar can be used uncompressed. It's just a container for files or a complete directory structure.

But you can combine tar and gzip (by using a command line switch to tar), to compress this structure in order to save memory.
 
domon said:
Julia download page mentions that v1.11 is for 13.2+. So even if downloading the full source tarball with dependencies from the download page (scroll down), I do not know if it will successfully build.

Searching the internet, I see that v1.7.x seemed to be the earliest version supported in FBSD 12 - speculating based on this old announcement. Unclear at which Julia version support for FBSD 12 got dropped, but here is the GH page that contains the full source tar for v1.7.3.

Note: I do not do Julia. Was just curious and had some time on hand to browse around.
Click to expand...
when you say that that tar contains the full source would that include the source for the dependencies? and would those files have to be compiled to get binary files that would work with the package function?
 
According to this "Building Julia" explanation, there are a number of programs that need to have already been installed in the machine you use to compile Julia. The compile (`make`) fails when one of them is missing on the machine.

"Building Julia requires that the following software be installed:

GNU make — building dependencies.
gcc & g++ (>= 7.1) or Clang (>= 5.0, >= 9.3 for Apple Clang) — compiling and linking C, C++.
libatomic — provided by gcc and needed to support atomic operations.
python (>=2.7) — needed to build LLVM.
gfortran — compiling and linking Fortran libraries.
perl — preprocessing of header files of libraries.
wget, curl, or fetch (FreeBSD) — to automatically download external libraries.
m4 — needed to build GMP.
awk — helper tool for Makefiles.
patch — for modifying source code.
cmake (>= 3.4.3) — needed to build libgit2.
pkg-config — needed to build libgit2 correctly, especially for proxy support.
powershell (>= 3.0) — necessary only on Windows.
which — needed for checking build dependencies."

That might be challenging if the machine cannot be connected to internet.
 
You must log in or register to reply here.
Back
Top