Install nRF Connect SDK v2.9.1 under Ubuntu 24.03.2 LTS

[Hiihtaja]

Hello !

Try to install latest nRF connect  to fresh notebook with latest Ubuntu LTS version.

And have got some known error;

• Failed to clone the repositories: Error: Cloning into '/home/user/ncs/v2.9.1/.west/manifest-tmp'... /home/user/ncs/toolchains/b77d8c1312/usr/local/libexec/git-core/git-remote-https: error while loading shared libraries: libunistring.so.2: cannot open shared object file: No such file or directory FATAL ERROR: command exited with status 128: git clone --branch v2.9.1 github.com/.../sdk-nrf /home/user/ncs/v2.9.1/.west/manifest-tmp Error: Launched process exited with non-zero status: 128 Error: Subprocess /home/user/.config/nrfconnect/nrfutil-sandboxes/toolchain-manager/0.15.0/bin/nrfutil-toolchain-manager failed with unexpected exit code Some(128)

Is any work around about it exists ? I need to use this LTS version ?

I have tried links creation from here but nothing dosn't help.

Regards,

Eugene

[runsiv]

Hi. 
Did you do has mentioned in this thread? I have reported the issue myself internally and it should be fixed in the next release of NCS. 

The fix in the mentioned thread worked for me on Ubuntu 24,044

Regards

Runar

[Hiihtaja]

Hi runsiv !

Could you point me to exact lines what should help for me.

links from libunistring.so.5 to 2 dosn't help.

and ncs filder is also empty, no way to delete/modify something inside.

Regards,

Eugene

[runsiv]

When I did my install of ubuntu 24 I think the following(Its some months since I did it so I can't exactly recall)

$ rm ~/ncs/toolchains/b81a7cd864/usr/lib/x86_64-linux-gnu/libpsl.so.5*

Just delete the NCS 2.x folder and restart the installation process

If that do not work, a co-worker said he created a symlink as mentioned here

sudo ln -s /usr/lib/libunistring.so.5.0.0 /usr/lib/libunistring.so.2
sudo ln -s /usr/lib64/libunistring.so.5.0.0 /usr/lib64/libunistring.so.2
sudo ln -s /usr/lib/libcrypt.so.2 /usr/lib/libcrypt.so.1
sudo ln -s /usr/lib64/libcrypt.so.2 /usr/lib64/libcrypt.so.1

The files is in the toolchain folder, you should still have them even if the SDK can't be installed

Regards

Runar

[Hiihtaja]

Hi runsiv ,

what do you think about latest preview release : https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/releases/release-notes-3.0.0-preview1.html

I'm able to install it without visible problem and try to build few samples right now,

Regards,

Eugene

[runsiv]

I think you can use it to download the older installations. In general the preview is in my opinion not something I would use for development as it is some time before the proper release of NCS 3.0. 
I will not be surprised if there are changes that will be described in the migration guide that can cause some issues, but this is only speculation on my part. 

Regards

Runar

[Hiihtaja]

Hi runsiv 

Looks like zephyr environment need extra tuning after automatic installation.

At list it is not the same experience what I had few year ago.

I expect to have command line building.

And even extra setting

source zephyr/zephyr-env.sh

export PYTHONHOME=/home/user/ncs/toolchains/aedb4c0245/usr/local/bin
export PYTHONPATH=/home/user/ncs/toolchains/aedb4c0245/usr/local/bin 

 and at folder

$ pwd
/home/user/ncs/v3.0.0-preview1/nrf/samples/crypto/aes_ccm

$ west build --pristine --board nrf52840dk_nrf52840
Python path configuration:
PYTHONHOME = '/home/user/ncs/toolchains/aedb4c0245/usr/local/bin'
PYTHONPATH = '/home/user/ncs/toolchains/aedb4c0245/usr/local/bin'
program name = '/usr/bin/python3'
isolated = 0
environment = 1
user site = 1
safe_path = 0
import site = 1
is in build tree = 0
stdlib dir = '/home/user/ncs/toolchains/aedb4c0245/usr/local/bin/lib/python3.12'
sys._base_executable = '/usr/bin/python3'
sys.base_prefix = '/home/user/ncs/toolchains/aedb4c0245/usr/local/bin'
sys.base_exec_prefix = '/home/user/ncs/toolchains/aedb4c0245/usr/local/bin'
sys.platlibdir = 'lib'
sys.executable = '/usr/bin/python3'
sys.prefix = '/home/user/ncs/toolchains/aedb4c0245/usr/local/bin'
sys.exec_prefix = '/home/user/ncs/toolchains/aedb4c0245/usr/local/bin'
sys.path = [
'/home/user/ncs/toolchains/aedb4c0245/usr/local/bin',
'/home/user/ncs/toolchains/aedb4c0245/usr/local/bin/lib/python312.zip',
'/home/user/ncs/toolchains/aedb4c0245/usr/local/bin/lib/python3.12',
'/home/user/ncs/toolchains/aedb4c0245/usr/local/bin/lib/python3.12/lib-dynload',
]
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

Current thread 0x00007ce8428da080 (most recent call first):
<no Python frame>

Looks like some post installation magic is need to set command line build environment

and it is not so clear from site documentation how to do it for current set of versions.

Do you have idea about it ?

Regards,

Eugene

[runsiv]

Hi. 

Can you try with nrfutil toolchain-manager launch --shell. If you get an issue then, you can try to set ZEPHYR_BASE

Regards

Runar