Hi, I’m completely new to Julia, I’d like to begging by expressing my appreciation for the FreeBSD installation package to the Dev responsible for it.
I’m under FreeBSD 14.3 patch 1. I’m using KDE, Plasma 6.4.3.
The way I installed Julia was that I downloaded the tar.gz for the last stable version (Version 1.11.6 (2025-07-09) Official https://julialang.org/ release for FreeBSD x86. I then proceeded, unpacked the tar within the command line in my ~/ directory. Then I looked inside the folder generated and placed the content of each folder in its corresponding folder in /usr/local/ [bin lib etc share include..] except for the .md file which I wasn’t sure where to put it. I then deleted the extracted folder and launched Julia by typing julia in the command line. Julia started normally, I gave the command ], came to the pkg mode and typed add Pluto, the installation started but stopped with an error message which is the following:
┌ Error: curl_multi_assign: 1===> ] 20/40
└ @ Downloads.Curl /usr/local/share/julia/stdlib/v1.11/Downloads/src/Curl/utils.jl:57
✓ ExproniconLite
[10757] signal 11 (1): Segmentation fault
in expression starting at none:0
curl_multi_socket_action at /usr/local/bin/../lib/libcurl.so.4 (unknown line)
curl_multi_socket_action at /usr/home/julia/.buildkite-agent/builds/freebsd13-amdci6-0/julialang/julia-release-1-dot-11/usr/share/julia/stdlib/v1.11/Downloads/src/Curl/Curl.jl:51 [inlined]
curl_multi_socket_action at /usr/home/julia/.buildkite-agent/builds/freebsd13-amdci6-0/julialang/julia-release-1-dot-11/usr/share/julia/stdlib/v1.11/Downloads/src/Curl/Curl.jl:59 [inlined]
macro expansion at /usr/home/julia/.buildkite-agent/builds/freebsd13-amdci6-0/julialang/julia-release-1-dot-11/usr/share/julia/stdlib/v1.11/Downloads/src/Curl/utils.jl:56 [inlined]
#55 at /usr/home/julia/.buildkite-agent/builds/freebsd13-amdci6-0/julialang/julia-release-1-dot-11/usr/share/julia/stdlib/v1.11/Downloads/src/Curl/Multi.jl:190
lock at ./lock.jl:232
#54 at /usr/home/julia/.buildkite-agent/builds/freebsd13-amdci6-0/julialang/julia-release-1-dot-11/usr/share/julia/stdlib/v1.11/Downloads/src/Curl/Multi.jl:188
unknown function (ip: 0x848e7495f)
jl_apply at /usr/home/julia/.buildkite-agent/builds/freebsd13-amdci6-0/julialang/julia-release-1-dot-11/src/julia.h:2157 [inlined]
start_task at /usr/home/julia/.buildkite-agent/builds/freebsd13-amdci6-0/julialang/julia-release-1-dot-11/src/task.c:1202
Allocations: 12157555 (Pool: 12155691; Big: 1864); GC: 21
Segmentation fault (core dumped)
here is the entire output from the installation processes of Pluto:
I also have to mention that prior to that manual installation I had installed Julia from the FreeBSD binary repository and I had no problem installing Pluto or running Julia but when trying to launch a page in Pluto via Firefox it crashed with segmentation fault if remember correctly. So I checked and Saw that it was better to install it manually with the latest version offer. I pkg remove and clean Julia and installed it manually. Didn’t reboot between the two installation.
As always thank you verry much for the support and again for providing a pkg version for FreeBSD users. Keep it free and awsome ! If further information are needed to help assisting I’ll be happy to provide them. Peace!
I don’t know why new users always prefer the archive installation over juliaup, but this is a recurrent issue. Please use juliaup.
To website maintainers:
Perhaps the official Julia website should hide the archives as a last resource in a separate section? Or at least add a warning in different color to make it clear that installing archives manually can lead to issues.
Hi @juliohm can you please explain why installing it manually is responsible for causing issue. because it should not? Until then I do not consider using juliaup as a solution and would like to fix manually. thanks
It should not be an issue, but it is in many cases, unfortunately. You can wait for other people to help you with the archive-based installation.
Search this forum and you will see many other threads where users attempted the archive-based installation, and after several attempts, just decided to choose the recommended method with juliaup.
@juliohm You’re conflating package managers (e.g., apt/rpm/homebrew/etc) with the official downloads. We do recommend against package managers like those. The problem is generally library version mismatch. Distros and 3rd party package managers like to treat dependencies like interchangeable lego blocks — and it often does cause errors like these.
Juliaup just automates downloading these official tarballs; I wouldn’t expect it to change anything in this case (but it could be helpful to check!).
This is indeed a problem with the official archive.
Thought it also configured environment variables like PATH. I’ve had Windows users complaining in various courses I gave in the past. The only way to get Julia working properly for them was juliaup.
In this case, the stack trace shows calling into a libcurl that’s living in /usr/local/lib/libcurl.so.4, which is likely to cause issues very much akin to those caused by package managers. I’m not sure why that would be happening. It is likely to be a configuration issue, and not likely to be one that juliaup would solve, but I hate speculating like this.
@redti: Do you have LD_LIBRARY_PATH set? What’s the full output of versioninfo()?
Why is it gonna cause trouble? The content of those folder is in each directory it is supposed to be. if were to install it with pkg it would have put them exactly there inst that true ? the folder in question could have been ported to pkg bin if I’m not mistaken ??
how to we know for sure that they are incompatible ? because they were built for an older version of FreeBSD ? so they interact with the libraries of the actual version causing bug, that’s it ? that’s the issue?
